Menu ▾ ▴

#2647 (ok 2.11.6) Display very large Queries

2.11.1.2
fixed
Marc Delisle
Data insertion/extraction/manipulation (334)
1
2013-06-11
2008-02-28
Sebastian Gebhard
No

I just imported some data from a SQL-Dump (GZip compressed) which included some "CREATE TABLE"s and many INSERTs.

Almost the complete dump was executed when this error occured:

#1153 - Got a packet bigger than 'max_allowed_packet' bytes

Ok, one of the INSERTs was too big, no problem.

But phpMyAdmin displayed this insert and that was a problem for my browser.

I think it's not very clever to display a command which is too big for the database.

I added a screenshot.

My suggestion is not to display the SQL when MySQL-Error #1153 occurs.

Discussion

  • Sebastian Gebhard

    Sebastian Gebhard - 2008-02-28

    Screenshot

     
    Thumbnail
    max_allowed_packet.gif

  • Jürgen Wind

    Jürgen Wind - 2008-02-28

    Logged In: YES
    user_id=1383652
    Originator: NO

    that's how *PHP* reacts when the gzip buffer overflows.
    use the "uploaddir" feature (see docs) and unzip the file (manually or by means of a php-script) before import.

     

  • Marc Delisle

    Marc Delisle - 2008-02-28
    • assigned_to: nobody --> lem9
     

  • Marc Delisle

    Marc Delisle - 2008-02-28
    • priority: 5 --> 1
    • summary: Display very large Queries --> (ok 2.11.6) Display very large Queries
    • status: open --> open-fixed
     

  • Marc Delisle

    Marc Delisle - 2008-04-29
    • status: open-fixed --> closed-fixed
     

  • Michal Čihař

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