On 28 Jan 2006, at 01:09, Randy J. Ray wrote:
Although - now that I've said all that - does the dbd interface
actually use sqlite3, or just version 2?
DBD::SQLite uses sqlite3.
Correct.
There's DBD::SQLite2 for those who have to use
sqlite2 for legacy purposes, but I'm pretty sure it isn'
> Although - now that I've said all that - does the dbd interface
> actually use sqlite3, or just version 2?
DBD::SQLite uses sqlite3. There's DBD::SQLite2 for those who have to use
sqlite2 for legacy purposes, but I'm pretty sure it isn't being maintained.
Randy
--
Maybe the perl interface always binds variables as strings. This
won't work - just like the second "SELECT count(*)" query below
didn't work as one might expect.
SQLite version 3.3.0
Enter ".help" for instructions
sqlite> create table ab(a,b);
sqlite> insert into ab values(1, 2);
sqlite> select c
Clark Christensen wrote:
What's not clear is whether the limitation is with SQLite, DBI, or DBD-SQLite,
or whether later revisions of any has enabled placeholders at that level.
Does sqlite3_prepare/step work with placeholders in the HAVING expression?
Clark,
The syntax description for the
Does sqlite3_prepare/step work with placeholders in the HAVING expression?
Thanks!
-Clark
- Original Message
From: David Cantrell <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Friday, January 27, 2006 6:30:14 AM
Subject: [sqlite] DBD::SQLite bug number 17292 - bounty!
Yes
Yesterday I reported this bug, where placeholders don't work in HAVING
clauses when using the DBD::SQLite module in perl. My lovely employers:
http://www.outcometechnologies.com/
have agreed to pay a bounty to whoever can fix this and have their patch
accepted by the DBD::SQLite maintainer.
The
6 matches
Mail list logo
