On Tue, 2007-01-09 at 08:01 -0800, Peter James wrote:
> On 1/9/07, Dan Kennedy <[EMAIL PROTECTED]> wrote:
> But it looks to me like commit #3341 (August 2006) covers this
> up. #3341
> changes things so that the shared-schema is reset whenever any
> connection
On Mon, 2007-01-08 at 16:03 -0800, Peter James wrote:
> Hey folks...
>
> The context of this message is sqlite library version 3.3.6, using the
> shared-cache mode, effectively following the test_server.c example.
> Immediately upon switching to shared-cache mode we started seeing errors
> like
On 1/8/07, Peter James <[EMAIL PROTECTED]> wrote:
Thanks for your response, Ken. I'm not sure I've explained myself
properly. It's not that I'm calling sqlite3_enable_shared_cache()
multiple times. It's that if I don't maintain a persistent connection while
the server is running I end up with
On 1/8/07, Ken <[EMAIL PROTECTED]> wrote:
You could always implement a sqlite3_open call and store it in the g
variable, and close it when the server quits.
Thanks for your response, Ken. I'm not sure I've explained myself
properly. It's not that I'm calling sqlite3_enable_shared_cache()
Here is a code snipet from my version if the server thread code
I found that it was doing an enable/disable on the shared cache with the
original logic.
You could always implement a sqlite3_open call and store it in the g variable,
and close it when the server quits.
void
5 matches
Mail list logo