![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Ok So I've been playing around with the MySQL server installation at my office. I managed to find a couple tools to help me play with the server. One is called HeidiSQL and the other is Navicat Lite. Navicat is a crippled version but still seems worth my while. While tinkering, I decided to import a table that I had previously exported from an access db. It is a list of zipcode, state, city with no index in the form of a csv file. This list is over 46000 records long. All seemed to go well and I was playing around with querying MySQL when suddenly I realized there was something wrong. The MySQL database only accepted 1000 records. I thought I had run into one of Navicat's crippled features, but when I tried to import it with HeidiSQL, I had the same problem. Only 1000 of the 46000 records were accepted by the MySQL server. Am I missing something? I looked around and found I could select different engines for different databases, but that didn't seem change anything. Maybe some setting I need to adjust that I overlooked? |
#3
| |||
| |||
|
|
In article<4d88cf25$0$27148$9a6e19ea (AT) unlimited (DOT) newshosting.com>, "Dr.X"<Dr.X@invalid> wrote: Ok So I've been playing around with the MySQL server installation at my office. I managed to find a couple tools to help me play with the server. One is called HeidiSQL and the other is Navicat Lite. Navicat is a crippled version but still seems worth my while. While tinkering, I decided to import a table that I had previously exported from an access db. It is a list of zipcode, state, city with no index in the form of a csv file. This list is over 46000 records long. All seemed to go well and I was playing around with querying MySQL when suddenly I realized there was something wrong. The MySQL database only accepted 1000 records. I thought I had run into one of Navicat's crippled features, but when I tried to import it with HeidiSQL, I had the same problem. Only 1000 of the 46000 records were accepted by the MySQL server. Am I missing something? I looked around and found I could select different engines for different databases, but that didn't seem change anything. Maybe some setting I need to adjust that I overlooked? Thanks group! -Dr.X If you import using MyPHPAdmin, do you have the same problem? Or you can use a LOAD directive from the mysql command line. If that limits your import, I'd look at the data or the import file you're running before pointing a finger at Navicat. |
#4
| |||
| |||
|
|
Perhaps record nr. 1001 does not have a valid format and the import process stops there, or it contains a record that does not fit in the column type you've chosen. Or you've chosen a small size for an autoincremental ID and you're running out of numbers. Importing CSV files is not so trivial. How are you doing it? |
#5
| |||
| |||
|
|
On 3/22/2011 1:04 PM, " lvaro G. Vicario" wrote: ... Perhaps record nr. 1001 does not have a valid format and the import process stops there, or it contains a record that does not fit in the column type you've chosen. Or you've chosen a small size for an autoincremental ID and you're running out of numbers. Importing CSV files is not so trivial. How are you doing it? HA! Mystery solved. *It turns out that all my queries were defaulting to a max return of 1000 records. *I should have been more observant of the SELECT statement the clients were using. *When I manually enter the commands, I get the results I expected of over 46000 records. Thanks for the response lvaro, and to everyone else that took the time to be helpful! -Dr.X |
#6
| |||
| |||
|
|
On Mar 22, 2:31*pm, "Dr.X" <Dr.X@invalid> wrote: On 3/22/2011 1:04 PM, " lvaro G. Vicario" wrote: ... Perhaps record nr. 1001 does not have a valid format and the import process stops there, or it contains a record that does not fit in the column type you've chosen. Or you've chosen a small size for an autoincremental ID and you're running out of numbers. Importing CSV files is not so trivial. How are you doing it? HA! Mystery solved. *It turns out that all my queries were defaulting to a max return of 1000 records. *I should have been more observant of the SELECT statement the clients were using. *When I manually enter the commands, I get the results I expected of over 46000 records. Thanks for the response lvaro, and to everyone else that took the time to be helpful! -Dr.X you know (or maybe you don't), there are lots of functions that can help... like: select count(*) from ziptable; Guess what it does??? |
![]() |
| Thread Tools | |
| Display Modes | |
| |