It's not recommended. Some operating systems (notably linux), have
problems releasing file-locks established by other threads.
You might be Ok on Windows, I'm not sure. But be careful, the
database locking might not work.
--- Cory Nelson <[EMAIL PROTECTED]> wrote:
> Yep, that's how I do it. Wo
Yep, that's how I do it. Works fine.
On 6/10/05, Brown, Dave <[EMAIL PROTECTED]> wrote:
>
> I read the docs on thread safety, where it says:
>
> "Threadsafe" in the previous paragraph means that two or more threads can
> run SQLite at the same time on different "sqlite" structures returned from
I read the docs on thread safety, where it says:
"Threadsafe" in the previous paragraph means that two or more threads can
run SQLite at the same time on different "sqlite" structures returned from
separate calls to sqlite_open(). It is never safe to use the same sqlite
structure pointer simultan
I got a grammar that looks like:
program ::= stmt.
stmt ::= A B.
stmt ::= error.
The log file shows this for state 0:
State 0:
program ::= * stmt
stmt ::= * A B
stmt ::= * error
A shift 2
error shift 4
4 matches
Mail list logo