ATutor

Learning Management Tools







Pages:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15


invalid mysql syntax


  • 2010-08-09 11:45:30

    invalid mysql syntax

    Hi,
    I am trying to import a course backed up from 1.6.1 import into 2.0.
    I am getting the following error :
    You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's sticking points and resistance to get to the turning point', 0, 0, 1)' at line 1
    Warning: Cannot modify header information - headers already sent by (output started at /home/lab/public_html/mods/_core/modules/classes/Module.class.php:829) in /home/lab/public_html/mods/_core/backups/restore.php on line 39

    As far as i can tell this is relating to the first line of one of the tables being imported.
    (first line of table is attached as a text file)
    Could this be casued by the fact that the data appears to be double quited CSV format, and the contents of my fields have both singe and double quotes?

    Thanks

    Matt

  • 2010-08-10 08:44:35

    Re: invalid mysql syntax

    Just spotted this as I was going through the old AT install :
    Patch 0002 :
    Fix these bugs:
    1. Patcher reports error "already installed" when installing a patch that have been installed before ATutor upgrade;
    2. When running on php4, content export feature gives a blank page;
    3. Content backup/restore does not perform correctly when characters " and , both presented;
    4. Course email page reports error when send-to member is not in a group;
    5. When importing scorm package, accept url encoded characters defined in href tag;
    6. Fix the bug that banner with special char is not restored correctly from backup;
    7. URL rewrite includes HTTP_HOST at parsing URL.

    Point 3, could this be the cause of my MySQL error?
    Is there a way to see what would be changed for this bit of the patch?

  • 2010-08-13 05:33:06

    Re: invalid mysql syntax

    Ok,
    Solved this by copying old install to new server along with database, and then upgrading it.