Re: [sqlite] sqlite3 and statement variables

2004-09-23 Thread Darren Duncan
At 11:12 PM -0700 9/22/04, Vladimir Vukicevic wrote: Ah, ok.. I assumed that since the mention of ?N and :N: was explicitly added for version 3 that it would be supported, but testing and looking at the code says otherwise. I'll rework my code to just use unnumbered params then. Thanks! -

Re: [sqlite] sqlite3 and statement variables

2004-09-23 Thread Vladimir Vukicevic
On Wed, 22 Sep 2004 22:53:19 -0700, Darren Duncan <[EMAIL PROTECTED]> wrote: > The documentation for SQLite 3 is very much out of date and needs to > be rewritten. In fact, a lot of the site documentation still refers > to SQLite 2. So you can't always trust what the documentation says > right

Re: [sqlite] sqlite3 and statement variables

2004-09-22 Thread Darren Duncan
At 10:20 PM -0700 9/22/04, Vladimir Vukicevic wrote: Howdy, I'm trying to prepare statements using the ?n and/or :N: notation mentioned in the documentation and the sqlite3.h header. However, trying something like "INSERT INTO foo VALUES( ?1 )" results in SQLITE_ERROR, with the error string being

Re: [sqlite] sqlite3 and statement variables

2004-09-22 Thread Vladimir Vukicevic
On Wed, 22 Sep 2004 22:32:51 -0700, Cory Nelson <[EMAIL PROTECTED]> wrote: > I was under the impression that the notation was just ? (no ending > number) and :AAA (no ending colon). Using it like that works fine for > me. Yep, plain unnumbered "?" works fine -- however, the docs and sqlite3.h

Re: [sqlite] sqlite3 and statement variables

2004-09-22 Thread Cory Nelson
I was under the impression that the notation was just ? (no ending number) and :AAA (no ending colon). Using it like that works fine for me. On Wed, 22 Sep 2004 22:20:46 -0700, Vladimir Vukicevic <[EMAIL PROTECTED]> wrote: > Howdy, > > I'm trying to prepare statements using the ?n and/or :N:

[sqlite] sqlite3 and statement variables

2004-09-22 Thread Vladimir Vukicevic
Howdy, I'm trying to prepare statements using the ?n and/or :N: notation mentioned in the documentation and the sqlite3.h header. However, trying something like "INSERT INTO foo VALUES( ?1 )" results in SQLITE_ERROR, with the error string being 'near "1": syntax error'. Similar results with