>Could you post it here? I bet I am not the only other one curious about it.
Here you go. I sent the same to Dr. Hipp, but I didn't hear anything
back. It would be nice to add this option to SQLITE since it is just
an additional TCL command switch.
If you want to see the difference, use a
Randall Fox wrote:
Do mind sharing or explaining your changes?
No.. But I should have gave more information. My changes were for
the TCL SQLITE code
If you are using TCL, let me know I can send you the code, which is
short and just adds another command line switch for the TCL sqlite3
>Do mind sharing or explaining your changes?
No.. But I should have gave more information. My changes were for
the TCL SQLITE code, and just affected the way TCL accesses the
library.
I was also getting the schema errors when I was using a single
threaded app. I was opening two instances but
Wow that's a lot different than what I
read in some of the messages I read in
the archive. I read that we're not
suppose to see SQLITE_SCHEMA errors
in SQLite3 unless something very wrong
happened.
Thanks,
Kervin
Dan Kennedy wrote:
There's a little bit written about SQLITE_SCHEMA errors here:
Jeff Thompson wrote:
The way THREADSAFE works currently, is that it must be defined, but
also must have a value assigned to it. The compiler switch /D
THREADSAFE won't cause sqlite to have thread safe code included, whiel
/D THREADSAFE=1 will. Ensure you're using the latter format, or
That was at
There's a little bit written about SQLITE_SCHEMA errors here:
http://www.sqlite.org/faq.html#q17
--- "Kervin L. Pierre" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks for your response. I'm at wit's end
> with this thing.
>
> I do open the database multiple times, but
> exactly once per
On Fri, 04 Feb 2005 16:54:31 -0500, Kervin L. Pierre
<[EMAIL PROTECTED]> wrote:
> Thanks for your response Chris.
>
> Is there a way to find out what components are
> compiled in at runtime?
>
I don't believe the way the THREADSAFE define is handled today would
allow you to check anything at
Hi,
Thanks for your response. I'm at wit's end
with this thing.
I do open the database multiple times, but
exactly once per thread. I then keep the
sqlite3* on thread local storage and only
use that pointer on the thread it was created
on. This is how I interpreted the documentation.
Is that
> I am using SQLite 3.0.8 in a Win32 threaded
> environment.
>
> I keep getting random "Database schema has changed"
> errors even though I am using thread local
> storage to make sure sqlite3_open() gets called
> on each thread and a there is a sqlite3* per thread.
>
> Has anyone had any luck
On Thu, 03 Feb 2005 14:15:52 -0500, you wrote:
>Hello,
>
>I am using SQLite 3.0.8 in a Win32 threaded
>environment.
>
>I keep getting random "Database schema has changed"
>errors even though I am using thread local
>storage to make sure sqlite3_open() gets called
>on each thread and a there is a
Hello,
I am using SQLite 3.0.8 in a Win32 threaded
environment.
I keep getting random "Database schema has changed"
errors even though I am using thread local
storage to make sure sqlite3_open() gets called
on each thread and a there is a sqlite3* per thread.
Has anyone had any luck with resolving
11 matches
Mail list logo
