Posts Topics Forums Images
Search videos from message boards Videos Search messages from microblogs Microblogs Search messages from imdb.com Imdb Search messages from yuku.com Yuku Search messages from lefora.com (free forums) Lefora
My account: Login | Sign Up
Loading... 

Thread: Query too long

Started 1 month ago by artcoder
I'm importing an SQL file using phpMyAdmin and it breaks in the middle of import giving me the error "#2006 - MySQL server has gone away". I believe it breaks while importing into the customer table and the SQL insert statement in the SQL file is very very long because it inserts many records in one statement. I understand that the person who exported the file should export it with separate...
Site: SitePoint : New Articles, Fresh Thinking for Web Developers and Designers  SitePoint : New Articles, Fresh Thinking for Web Developers and Designers - site profile
Forum: MySQL  MySQL - forum profile
Total authors: 3 authors
Total thread posts: 4 posts
Thread activity: no new posts during last week
Domain info for: sitepointforums.com

Other posts in this thread:

r937 replied 1 month ago
when you have a long series of values... Code: INSERT INTO sometable (column, column, column, ... ) VALUES ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ... you can easily ...

artcoder replied 1 month ago
I splitted the SQL statement and then got "max execution time exceeded" error. So I then splitted in into multiple SQL files. And I also had to use TypePad in order to be able to handle editing the large text file. But it finally worked. Thanks.

PHPycho replied 1 month ago
It's more effective to use mysql command line for import which can handle GB of data with ease. In case of phpMyAdmin you should increase the max post upload size & maximum execution time for handling large data.

 

Top contributing authors

Name
Posts
artcoder
2
user's latest post:
Query too long
Published (2009-11-14 22:43:00)
I splitted the SQL statement and then got "max execution time exceeded" error. So I then splitted in into multiple SQL files. And I also had to use TypePad in order to be able to handle editing the large text file. But it finally worked. Thanks.
r937
1
user's latest post:
Query too long
Published (2009-11-14 21:47:00)
when you have a long series of values... Code: INSERT INTO sometable (column, column, column, ... ) VALUES ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ( value, value, value, ... ) , ... you can easily break it up just by adding a new INSERT line as often as you wish -- say,...
PHPycho
1
user's latest post:
Query too long
Published (2009-11-16 01:23:00)
It's more effective to use mysql command line for import which can handle GB of data with ease. In case of phpMyAdmin you should increase the max post upload size & maximum execution time for handling large data.

Related threads on "SitePoint : New Articles, Fresh Thinking for Web Developers and Designers":

Related threads on other sites:

Thread profile page for "Query too long" on http://www.sitepointforums.com. This report page is a snippet summary view from a single thread "Query too long", located on the Message Board at http://www.sitepointforums.com. This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity