RE: [sqlite] Error on commit
> -Original Message-
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 02, 2004 4:26 AM
> To: Williams, Ken
> Cc: SQLite-Users (E-mail)
> Subject: Re: [sqlite] Error on commit
>
>
> On 29 Jan 2004, at 18:23, Williams, Ken wrote:
>
> >create_new_sqlite_database();
> >$dbh->do("BEGIN");
> >add_lots_of_rows_to_lots_of_tables();
> >$dbh->do("COMMIT");
>
> Change to:
>
>create_new_sqlite_database();
>$dbh->{AutoCommit} = 0;
>add_lots_of_rows_to_lots_of_tables();
>$dbh->commit;
># Optionally...
>$dbh->{AutoCommit} = 1;
Right, I've made that change (see a previous message) but it doesn't seem to
have any effect on this situation.
The real problem seemed to be that I was out of disk space, and the SQLite
error message to that effect (if any) was missing.
-Ken
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [sqlite] Error on commit
On 29 Jan 2004, at 18:23, Williams, Ken wrote:
create_new_sqlite_database();
$dbh->do("BEGIN");
add_lots_of_rows_to_lots_of_tables();
$dbh->do("COMMIT");
Change to:
create_new_sqlite_database();
$dbh->{AutoCommit} = 0;
add_lots_of_rows_to_lots_of_tables();
$dbh->commit;
# Optionally...
$dbh->{AutoCommit} = 1;
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [sqlite] Error on commit
> Don't know anything about the DBD::SQLite extension. Is there a > separate mailing list for that? Seems like DBD::SQLite is hosted > on sourceforge, isn't it? Probably ought to ask there. There's no separate mailing list, just a bug tracker at http://rt.cpan.org/ . I know Matt reads this list (at least occasionally), but he's got a million projects. > It is possible for a COMMIT to fail because you either > ran out of disk space or memory. But those errors are > much more likely to occur while you are doing INSERTs. > By the time you get to the COMMIT, most (or all) of the > disk and memory space has already been allocated. Hmm, it seems like it was probably a disk space issue - I know it was quite tight when I was running these queries, and later on things mysteriously started working again. I'm a little hesitant to write scripts to test this theory, but it seemed like if disk space ran out at the wrong time, sqlite failed in a nonobvious way. I'm thinking this has to do with hard vs. soft quotas - perhaps filehandles that were already open were succeeding, but no new writes worked? I'm working on a solaris 7 box at the moment. -Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [sqlite] Error on commit
> -Original Message-
> From: Helphand [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 29, 2004 8:06 PM
> To: Williams, Ken; SQLite-Users (E-mail)
> Subject: Re: [sqlite] Error on commit
>
>
> At 12:23 PM 1/29/04 -0600, Williams, Ken wrote:
>
> >create_new_sqlite_database();
> >$dbh->do("BEGIN");
> >add_lots_of_rows_to_lots_of_tables();
> >$dbh->do("COMMIT");
> >
>
> The correct syntax is;
>
> $dbh->begin_work;
>
> $dbh->commit;
Yeah, I made that switch yesterday actually, and it didn't change anything.
-Ken
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [sqlite] Error on commit
At 12:23 PM 1/29/04 -0600, Williams, Ken wrote:
create_new_sqlite_database();
$dbh->do("BEGIN");
add_lots_of_rows_to_lots_of_tables();
$dbh->do("COMMIT");
The correct syntax is;
$dbh->begin_work;
$dbh->commit;
Try them.
Scott
Utilities for POPFile, the OpenSource Mail Classifier
http://www.geocities.com/Helphand1/popfile.htm
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [sqlite] Error on commit
Williams, Ken wrote:
Hi,
I'm using DBD::SQLite compiled with SQLite version 2.8.11. I'm getting the
following error, with RaiseError => 1:
DBD::SQLite::db do failed: at load_db.pl line 27, <$in_file> line
220663.
(Line 27 is simply $dbh->do("COMMIT"); )
So,
A) Why isn't the error string being displayed as part of the error?
Don't know anything about the DBD::SQLite extension. Is there a
separate mailing list for that? Seems like DBD::SQLite is hosted
on sourceforge, isn't it? Probably ought to ask there.
B) What might be actually causing the commit to fail? There is 1 active
transaction at this point in the code, and no previous transactions. My
script boils down to the following pseudocode:
create_new_sqlite_database();
$dbh->do("BEGIN");
add_lots_of_rows_to_lots_of_tables();
$dbh->do("COMMIT");
It is possible for a COMMIT to fail because you either
ran out of disk space or memory. But those errors are
much more likely to occur while you are doing INSERTs.
By the time you get to the COMMIT, most (or all) of the
disk and memory space has already been allocated.
I'm guessing some kind of DBD::Sqlite problem here.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[sqlite] Error on commit
Hi,
I'm using DBD::SQLite compiled with SQLite version 2.8.11. I'm getting the
following error, with RaiseError => 1:
DBD::SQLite::db do failed: at load_db.pl line 27, <$in_file> line
220663.
(Line 27 is simply $dbh->do("COMMIT"); )
So,
A) Why isn't the error string being displayed as part of the error?
B) What might be actually causing the commit to fail? There is 1 active
transaction at this point in the code, and no previous transactions. My
script boils down to the following pseudocode:
create_new_sqlite_database();
$dbh->do("BEGIN");
add_lots_of_rows_to_lots_of_tables();
$dbh->do("COMMIT");
Thanks,
-Ken
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
