8:30:10 PM
Subject: Re: [sqlite] DBD::SQLite 1.14 prepare_cached bug?
I think i found solution.
The problem is that DBD::SQlite->disconnect() method execute
sqlite3_close() function.
This function return SQLITE_BUSY in case if there are any active statement.
>From API:
"Applicatio
I think i found solution.
The problem is that DBD::SQlite->disconnect() method execute
sqlite3_close() function.
This function return SQLITE_BUSY in case if there are any active statement.
>From API:
"Applications should finalize all prepared statements and close all
BLOBs associated with the
Hello,
> What do you expect to see? From the code, I'm guessing something like:
This is "test-case" program for testing DBD-SQLite behavior. Dumper is
only for be sure, that data was read correctly from database.
> If you're just trying to silence the "closing dbh with active handles..."
>
Sorry, this was mis-addressed. Should have gone to the list...
- Forwarded Message
From: Clark Christensen <[EMAIL PROTECTED]>
To: Alexander Batyrshin <[EMAIL PROTECTED]>
Sent: Monday, February 4, 2008 9:46:49 AM
Subject: Re: [sqlite] DBD::SQLite 1.14 prepare_cached bug?
ba
Opss. Code with numbers looks like this:
$sth->execute;
my ($val) = $sth->fetchrow_array;
#[1] my ($val2) = $sth->fetchrow_array;
#[2] $sth->finish;
___
sqlite-users mailing list
sqlite-users@sqlite.org
Hello All,
I don't know is it right place to discuss this or not. Sorry If I am
doing something wrong.
Installed sqlite-3.5.4 and DBD::SQLite-1.14
I get problems with this code:
%<
#!/usr/bin/perl -w
use strict;
use DBI;
use Data::Dumper;
use
6 matches
Mail list logo
