Skip Menu |

This queue is for tickets about the DBD-SQLite CPAN distribution.

Report information
The Basics
Id: 53579
Status: resolved
Priority: 0/
Queue: DBD-SQLite

People
Owner: Nobody in particular
Requestors: whatever [...] davidnicol.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 1.25
Fixed in: 1.29



Subject: minor remaining extended placeholder DWIM issue (but workaround available in recent ver is okay, THANKS!)
the sqlite3 command line utility supports placeholders by using for instance ?1 to mean the first argument, as if hook was the placeholder sygill. The DBI docs say use :1 but it isn't portable. Well, neither works with DBD::SQLite 1.25. I'll try upgrading. ... Okay, an update of the form update TABLE set a=? where b=? and a IS NOT :1 compiles but wants four args as if the :1 is a fourth ? but update TABLE set a=:1 where b=:2 and a IS NOT :1 works as intended, so that's fine. Also, there doesn't seem to be any mention of "placeholder" anywhere in the pod, to state what will and won't go as a placeholder with this DBI driver. Good times!
Hi. 1.30_01 has a short note and a test on this matter. If they're not enough for you, please send us a patch or just reopen this. Thanks. On 2010-1-10 Sun 19:04:44, DAVIDNICO wrote: Show quoted text
> the sqlite3 command line utility supports placeholders by using for > instance ?1 to mean the first argument, as if hook was the placeholder > sygill. The DBI docs say use :1 but it isn't portable. Well, neither > works with DBD::SQLite 1.25. I'll try upgrading. ... > Okay, an update of the form > > update TABLE set a=? where b=? and a IS NOT :1 > > compiles but wants four args as if the :1 is a fourth ? > > but > > update TABLE set a=:1 where b=:2 and a IS NOT :1 > > works as intended, so that's fine. > > Also, there doesn't seem to be any mention of "placeholder" anywhere
in Show quoted text
> the pod, to state what will and won't go as a placeholder with this
DBI Show quoted text
> driver. > > Good times!