Don't go drawing conclusions that may be premature. Dig deeper first.
(Perl can get confused about line numbers in some cases.)
Use $SIG{__WARN__} = sub { ... } and Carp::confess and Data::Dumper
to dump the stack and all the relevant data at the exact point it happens.
Reproduce the problem with a smaller data set (using the above info)
so it can be reproduced more easily. Enable tracing. Etc etc.
Tim.
p.s. quoting performance figures is generally meaningless.
On Wed, Nov 17, 2004 at 08:40:39PM +1100, Ron Savage wrote:
> Hi Folks
>
> I've just run a test on a Pentium III @ 800 MHz.
>
> Transactions were not used, in order to stress SQLite.
>
> Importing the data from various text and spreadsheet files took 3 h 24 m.
>
> This is Perl 5.8.4.
>
> During this, I got 4 identical messages which said:
>
> Use of an uninitialized value in subroutine entry at
> f:/Perl/site/lib/Project/Populate.pm line 2440
>
> The subroutine within which this line occurs is only ever called once.
> It's entry point:
> my($self) = @_;
> is at line 1530 (sic).
>
> Around line 2440 we have:
> 2435 (blank)
> 2436 my($sql) = '...';
> 2437 my($sth) = $self -> prepare($sql); # sic. $self, not $dbh.
> 2438 $count = 1;
> 2439 %count = ();
> 2440 (blank)
> 2441 # A comment
> 2442 # A comment
> 2443 $sth -> execute(...);
>
> There should be no such error msg referring to line 2440.
>
> When importing into MySQL, there is no such error.
>
> I take this error to mean SQLite or DBD::SQLite is corrupting Perl's memory.
>
> The read-only app which uses this database seems to work, in that I have not
> yet detected problems with it, although testing has so far been very limited.
>
> My conclusion regarding the warning messages is the SQLite cannot be relied
> upon, under Windows, and hence should not be used in production.
>
> One test I could do is export the SQLite database as a text file, and compare
> with an export from the MySQL version.
>
> I am not yet in a position to run an identical import - not export - test
> under GNU/Linux, but I'm aiming to do so this year.
>
> --
> Cheers
> Ron Savage, [EMAIL PROTECTED] on 17/11/2004
> http://savage.net.au/index.html
>
>
