On 10/06/2009 9:02 AM, Igor Tandetnik wrote:
> Jeremy Smith wrote:
>> John Machin wrote:
>>> On 10/06/2009 4:40 AM, Jeremy Smith wrote:
>>>
When I run sqlite3_interrupt, it doesn't close existing file
handles, making further searches tricky.
>>> Which handles? How do you know? What
Jeremy Smith wrote:
> John Machin wrote:
>> On 10/06/2009 4:40 AM, Jeremy Smith wrote:
>>
>>> When I run sqlite3_interrupt, it doesn't close existing file
>>> handles, making further searches tricky.
>>>
>>
>> Which handles? How do you know? What does "tricky" mean -- "difficult
>> but I can cope
John Machin wrote:
> On 10/06/2009 4:40 AM, Jeremy Smith wrote:
>
>> When I run sqlite3_interrupt, it doesn't close existing file handles,
>> making further searches tricky.
>>
>
> Which handles? How do you know? What does "tricky" mean -- "difficult
> but I can cope with it" or "causes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Smith wrote:
> When I run sqlite3_interrupt, it doesn't close existing file handles,
Why would it? sqlite3_interrupt sets a flag on the sqlite3 handle.
Various operations periodically check the flag and if it is true then
error out with
On 10/06/2009 4:40 AM, Jeremy Smith wrote:
> When I run sqlite3_interrupt, it doesn't close existing file handles,
> making further searches tricky.
Which handles? How do you know? What does "tricky" mean -- "difficult
but I can cope with it" or "causes an error" (if so, which?) or
something
When I run sqlite3_interrupt, it doesn't close existing file handles,
making further searches tricky. So I wrote code which clears all normal
file handles (fopen in shell.c), but...
How do I close the database file too? It's not opened using fopen, but
with CreateFileA (in winOpen in os_win.c)
6 matches
Mail list logo