>> Drat. It doesn't look like there's a way to see what's already been
>> bound to a statement either, correct?
See this thread for a previous disuccsion of the problem:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg28610.html
Ralf
___
On May 18, 2008, at 12:01 AM, Shawn Wilsher wrote:
> On Sat, May 17, 2008 at 10:13 AM, Dan <[EMAIL PROTECTED]> wrote:
>> How are you going to 'clone' the statement objects to pass to
>> the second database handle?
> Our wrapper around the statement object already stores the string of
> the sql
On Sat, May 17, 2008 at 10:13 AM, Dan <[EMAIL PROTECTED]> wrote:
> How are you going to 'clone' the statement objects to pass to
> the second database handle?
Our wrapper around the statement object already stores the string of
the sql statement, so that part is easy. Looks like we'll have to
On May 17, 2008, at 7:59 PM, Shawn Wilsher wrote:
> On Sat, May 17, 2008 at 2:39 AM, Dan <[EMAIL PROTECTED]> wrote:
>>> And a fun follow-up question. Will sqlite3_transfer_bindings
>>> transfer
>>> bindings across connection objects if the two statements are for two
>>> different connections
On Sat, May 17, 2008 at 2:39 AM, Dan <[EMAIL PROTECTED]> wrote:
>> And a fun follow-up question. Will sqlite3_transfer_bindings transfer
>> bindings across connection objects if the two statements are for two
>> different connections to the same database?
>
> No. It will return SQLITE_MISUSE.
On May 17, 2008, at 2:51 AM, Shawn Wilsher wrote:
> And a fun follow-up question. Will sqlite3_transfer_bindings transfer
> bindings across connection objects if the two statements are for two
> different connections to the same database?
No. It will return SQLITE_MISUSE.
Dan.
>
> Cheers,
And a fun follow-up question. Will sqlite3_transfer_bindings transfer
bindings across connection objects if the two statements are for two
different connections to the same database?
Cheers,
Shawn
On Tue, May 13, 2008 at 2:05 PM, Shawn Wilsher <[EMAIL PROTECTED]> wrote:
> I was looking through
We most certainly are using sqlite3_prepare_v2. This use case is a
bit more exotic.
We are currently working on an async database access API (discussion
thread [1]). The idea is to have a user prepare and bind parameters
on the calling thread, then clone that statement to send it to the
On May 13, 2008, at 2:05 PM, Shawn Wilsher wrote:
> I was looking through the documentation and was wondering why
> sqlite3_transfer_bindings has been marked as obsolete. It's something
> that we use currently in our code, and I was looking to use it again
> for something new. Is there a new
I was looking through the documentation and was wondering why
sqlite3_transfer_bindings has been marked as obsolete. It's something
that we use currently in our code, and I was looking to use it again
for something new. Is there a new way to accomplish the same thing
that this function does?
10 matches
Mail list logo
