Unsupported Screen Size: The viewport size is too small for the theme to render properly.

New problem with SJA

  • This topic is empty.
Viewing 8 reply threads
  • Author
    Posts
    • #9084
      peterlaursen
      Participant

      @ Ritesh

      I am sorry (and also somewhat tired!) 'bout this …

      1) When running SJA (4.07 RC2) from GUI it does:

      Table SrcRows TgtRows Inserted Updated Deleted

      ========================= ======= ======= ======== ======= =======

      `mp3_filer` 38499 38482 0 0

      Total time taken – 8 sec(s)

      (and nothing has happened)

      Did you forget setting to \\ with the LIKE-parser in the GUI-version of the code ?

      2) When running from command-line (with the same jobfile!)

      Sync started at Mon Jul 04 12:25:02 2005

      Table SrcRows TgtRows Inserted Updated Deleted

      ========================= ======= ======= ======== ======= =======

      `mp3_filer` 38499 38482 17 0 0

      Total time taken – 60 sec(s)

      3) Even more mystical: Changing PK from 'filnavn' to 'Guid' and deleting the 17 rows again: it (commandline)displays,

      Sync started at Mon Jul 04 12:30:32 2005

      Table SrcRows TgtRows Inserted Updated Deleted

      ========================= ======= ======= ======== ======= =======

      `mp3_filer` 38499 38482 16 0 0

      Total time taken – 55 sec(s)

      4) Changing PK back to 'filnavn' and running the sync again the row omitted before gets inserted ..

      You can try yourself form my webhost …

      execute this SQL first: DELETE from mp3_filer where kunstner ='abaji';

      It is with completely fresh data dumped and uploaded 20 minutes ago (just to be sure).

      Jobfile looks like:

      *****

      Code:





      localhost
      ******** ******** 3306 musik



      http://www.deepeter.dk/SQLyogTunnel.php
      -2101821

      mydb1.surftown.dk
      ********** ********** 3306 jazcyk_test

      `mp3_filer`
      `ModTime`


      I will check if I can see something special about the row that is being omitted.  I have some idea about which one it is …

    • #18461
      peterlaursen
      Participant

      Just as I thought – the one missing was the one with this 'filnavn':

      M:Peters MusikAntologierRêves d'Oasis Desert Blues 2 (1 of 2)7 Gibran.mp3

      escaping problem with d'Oasis when 'filnavn' not PK ? ??

      NOTE: string d'Oasis occurs in more colums …

    • #18462
      royvarley
      Member

      I'm getting similar problem on sync jobs.

      When a data item contains ' I get an error in the log file:

      Error No. 1064

      You have an error in your SQL syntax near 's Quarry', `CostumeDescription`=NULL, `CompanyID`='1', `ProjectID`='15', `Sectio' at line 1

      The data in the field was Mr Slate's Quarry

      The record containing this field does not update.

    • #18463
      peterlaursen
      Participant

      the ' -character must be escaped too so a true statement with your data would go

      Quote:
      select 'Mr Slate's Quarry' like '%\'%'

      But all that should now be transparently handlet by SJA-sync (since 4.06 or maybe 4.07 as far as I remember). I do sync with these data regularly and have not observed any error. But I have hundreds of data to test with and shall do it If only you answer this

      Which version of SQLyog are you using?

      Would you mind pasting in the definition for the table ?

    • #18464
      peterlaursen
      Participant

      I can't reproduce the problem with 4.1 beta6!

      Look at picture – there are lot's of apostrophs.

      If I make a copy of that table and remove the ” ' “s from all data in the copy and run sync they are correctly sync'ed back to to data with apostroph's.

      this one

      Quote:
      `ProjectID`='15'

      really surprises me. '15' is a string ??

      and this one

      Quote:
      `Sectio'

      even more! starts with backquote and ends with apostroph ??

      Do you use columns_selection or sql_where ?

    • #18465
      royvarley
      Member

      Sorry – SJA 4.05

      In this case, Columns selection and SQL Where not used.

      But since you say that should have been fixed at 4.06/07, I guess I'll try that.

    • #18466
      royvarley
      Member

      Tried with 4.07 download. SJA reports V4.1

      Same problem.

      Note that the error message puts single quotes around the text where it thinks there's an error. So the leading quote at 's Quarry and the trailing quote at Sectio' were supplied by SJA error reporting. '15' is ok – it's common practice to quote numerics in a SQL statement.

    • #18467
      Ritesh
      Member

      Have you tried with the Windows version?

      BTW, can you mail me sample data to reproduce the error?

    • #18468
      royvarley
      Member

      Ritesh, I'll start a new post for my issue – I hadn't intended to hijack Peter's thread, I thought it was the same problem – but maybe not.

Viewing 8 reply threads
  • You must be logged in to reply to this topic.