#3161 #1064 bug in the SQL parser

3.3.8
fixed
nobody
7
2013-06-11
2010-12-20
Yonatan P
No

Steps done:
1. databases export + gzipped
2. database import
what happened:
the import have failed with the following:

Error
There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:
----BEGIN CUT----
eNpzDQryD7JScDZUcDZS8HH1s1IwUDBUMDE25woOAYrLc3EFhwEFVTxTVLh8K4MDfawUTPUM9EwN
E3WT83NzS/MySyp1c/LTuUKDgxT8g3UUHN1d/UJ0FMJcgbrDM/MUPF0VLPQMuAJ8Ha0UjPWM9Sz0
DLkCPAJACnT8g0GmGekZmij4ZOaVVnD5OPq5Wymk5umWlqTpWnCBrZPv5mAAA+Y3f2/PSjs+UZbj
3vXgP4dqjqqENh74ttl6VMGoAuoqAABkZj5d
----END CUT----
----BEGIN RAW----

ERROR: C1 C2 LEN: 0 1 437
STR: 

SVN: $Id$
MySQL: 5.0.51a-community-log
USR OS, AGENT, VER: Win IE 8.0
PMA: 3.3.8.1
PHP VER,OS: 5.2.14 Linux
LANG: en-utf-8
SQL: ���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;���ۚfǑ��S��|�$U����;----END RAW----

SQL query:

���ۚfǑ��S��|�$U����;

MySQL said:

#1064 - 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 '‹' at line 1

-----
while this is going on from phpMyAdmin , i was able to create and restore a gzipped database manually.

-----
Plaintext restore works correctly.
-----
php.ini settings:

max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 120 ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 196M ; Maximum amount of memory a script may consume (128MB)

apache is set to keepalive on

what can be done to resolve this situation and to get phpmyadmin work with gzipped importing.

Thank you for any suggestions!

Discussion

  • Yonatan P

    Yonatan P - 2010-12-20
    • priority: 5 --> 7
     
  • Marc Delisle

    Marc Delisle - 2010-12-22

    I cannot reproduce this problem. Was the export gzipped by phpMyAdmin directly?

    Does a similar export done from just one table have the same problem?

     
  • Yonatan P

    Yonatan P - 2010-12-23

    Hello,
    the export is done Directly from PhpMyAdmin,
    the export took place from the same server locally, and from another server - in both cases the import failed.
    after trying to export a single table gzipped, and importing it i still get an error.

    SQL query:

    ���[w�H�6�����nޙo5��qf�Z�,�˲5����DBJ$�I����Dd" ��w_�]��DfFd���L^==<]l�f�z���?�z�Y<�m2y�\���Y�R�P����_=��O��y///����ؖ�K�XVk�C��f���W�fZ���W�eՖk�ԋ�?^����B��W����+?�(xuy���j��?�?^�����O��p�����D������������?_�g���Z�~��o��_�����������7����D�ӂW� ����7���W����Ƿ_n����߱������$����~��>����1���?��|�������9~ ��}���������.�?�N�M�.o���O�r�cYl��M9���`�������v^�Z���t�i�WwM�j���r�*�m9�.�����Wo�n޾�9{����^}�z����״'������ ���׳?^�����_���ϟ_��uS��i[-�����o��E5������ ~Ħ���j]�X��6�y��x'�Ͳ�6���և�z]�7���ͪ�r3_��?���|y�����^���^������o����������볋W�޼}wF��� ���Y���_�r�j�B�y��EA���;�l��5��?u$�\���y����ב3�������]���������+����[��W$����1E����J̀����p1'��c�ZM��f����?�����zH�D�6 ���ȋR�nc�4Y?T�Y}wW��rZ�h9a戥���j'm��'eCpˆp7�Y��ÿ��RG�$�V�'B\�m�L�C���(q�O���dU�v��_��Bb���\&gt;�v1��yw��{h�-_�;:���K��#I�$p��y�z����;0�� s� �fu���r9�̪r��ZaEC�%�F�6 O_�B_�e��Xo��V�xX/v��}LdhO�ϟeA�9[...]

    MySQL said:

    #1064 - 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 '‹' at line 1

    what could this be related to?

    I cannot see no php errors

    apache log:

    [23/Dec/2010:13:41:52 +0100]
    "POST /phpmyadmin/import.php"
    db_import.php?phpmyadmin/db=db_upload&server=1&token=e4f0c1cdd227706b55d14226dc0a8f49"

    [23/Dec/2010:13:42:20 +0100]
    GET /phpmyadmin/themes/original/img/s_error.png HTTP/1.1" 200 548 "http://www.example.com/phpmyadmin/import.php"

    seems to take about 30 seconds from post to error.

     
  • Marc Delisle

    Marc Delisle - 2010-12-23

    Can you reproduce this problem on http://demo.phpmyadmin.net/ if you choose the latest stable release?

     
  • Marc Delisle

    Marc Delisle - 2011-04-19
    • status: open --> pending
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     
  • Michal Čihař

    Michal Čihař - 2013-06-11
    • Status: closed --> fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks