On 30/01/2009 2:27 AM, Mike Eggleston wrote:
> On Thu, 29 Jan 2009, Thomas Briggs might have said:
>
>> When you say the load "stops", what do you mean? Does the sqlite3
>> process end? Does it sit there doing nothing?
>>
>> The first thing I would do is look at line 55035 of the source file
>> and see if there's something weird about it.
>>
>> Also, have you done a line count on the file so you know exactly
>> how many rows it should load?
>>
>> -T
>>
>> On Wed, Jan 28, 2009 at 5:33 PM, Mike Eggleston <mikee...@me.com> wrote:
>>> Hi,
>>>
>>> I'm curious how sqlite3 may perform for some of my applications that
>>> really don't need things like MySQL or larger. I am using bacula
>>> (http://www.bacula.org) at work so I dumped the bacula data from MySQL
>>> (mysqldump bacula > bacula.sql), wrote a perl script to massage the data,
>>> and now I'm trying to load that data into a sqlite3 file.
>>>
>>> I don't see any errors on stdout, but the loading of rows stops after
>>> 55034 rows (file size is 6338560 bytes). I know in MySQL this table
>>> has rows.
>>>
>>> Where can I look and what might be the error that the rows are not
>>> loading?
>>>
>>> Mike
>>>
>>> Fedora Core 5
>>> sqlite3 3.3.3
>
> After deleting the three rows in my previous message (that has not yet
> made it through moderation), the load now stops at 6337536 bytes when
> using the command 'time sqlite3 x.db < x.sql ; date'. Still no messages
> nor errors from sqlite to stdout nor stderr from the above command.
>
> What to try next?
Have you looked at the stoppage points in your file(s) with a hex
editor? Any non-printable non-ASCII characters other than newline ('\n')?
[If you were on Windows I'd bet you had Ctrl-Z aka '\x1a' aka CPMEOF
bytes in there]
You could also try answering Thomas Briggs's questions:
(1) When you say the load "stops", what do you mean? Does the sqlite3
process end? Does it sit there doing nothing?
(2) Also, have you done a line count on the file so you know exactly how
many rows it should load?
Also while you are getting the line count from wc, get the character
count and compare it with the file size from ls.
And another thought, bit of a long shot, try running it without the
"time" and "; date".
Oh, and try running it with only the 3 lines that you cut out plus a
couple more on the end. If that reproduces the problem, then at least
you don't have to wait around while experimenting. The next experiment
would be to try to reproduce the problem with a non-confidential set of
5 or so lines so that you could post it here for scrutiny.
And double-check the SQL syntax in the 3 lines that you cut out.
HTH,
John
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
