Il 17/08/2010 11.21, Dan Kennedy ha scritto:
>> I'm using SQLITE_STATIC since the memory buffer returned by
>> cStringUsingEncoding should be valid until the object is deallocated,
>> which doesn't happen until after the statement is executed.
>>
> You could try using SQLITE_TRANSIENT instead
> I'm using SQLITE_STATIC since the memory buffer returned by
> cStringUsingEncoding should be valid until the object is deallocated,
> which doesn't happen until after the statement is executed.
You could try using SQLITE_TRANSIENT instead to verify this.
Or just go straight to valgrind.
memory buffer returned by
cStringUsingEncoding should be valid until the object is deallocated,
which doesn't happen until after the statement is executed.
Thanks for your help.
> From: sqlite-users-boun...@sqlite.org on behalf of Dario Napolitano
> Sent: Mon 8/16/2010 11:33 AM
> To: sqlit
Il 16/08/2010 21.04, Simon Slavin ha scritto:
> Where is the sqlite3_open command used ? Is it in the main thread or
> the writing thread ?
The main thread calls sqlite3_open, then registers a custom collation
function and creates the tables. The connection handle is then passed to
the worker
On 16 Aug 2010, at 5:54pm, Black, Michael (IS) wrote:
> The SQLite
> connection is created on the main thread and then handed off to the
> writing thread which is the only one to use it.
Where is the sqlite3_open command used ? Is it in the main thread or the
writing thread ?
Does the
8/16/2010 11:33 AM
To: sqlite-users@sqlite.org
Subject: EXTERNAL:[sqlite] Record corruption on Mac OS X 10.6 (Snow Leopard)
Hello everyone.
I have developed a conversion tool to generate a SQLite database from a
MySQL one. The tool is a simple C Cocoa application in which I have
statically
6 matches
Mail list logo
