I'm contemplating using the TCL binding of sqlite, but the database is to
be located in a shared folder and about 100 users will be accessing it for
read/write purposes. I would like to take some time to learn as much as
possible to safeguard the database from getting corrupt due to
Stefano Barbato wrote:
is there a way to detect at runtime if the sqlite library has been compiled
with the THREADSAFE=1 flag or not?
No, or not that I know of. It would be nice for ver 3 to have a simple
function which returns a structure of the database library capabilities.
The obvious ones
> I'm contemplating using the TCL binding of sqlite, but the database is to
> be located in a shared folder and about 100 users will be accessing it for
> read/write purposes. I would like to take some time to learn as much as
> possible to safeguard the database from getting corrupt due
Hi,
I already tried to find the aswer on the faq/wiki/mailing list archive/google
with no luck so here is my question:
is there a way to detect at runtime if the sqlite library has been compiled
with the THREADSAFE=1 flag or not?
I need thread-safeness turned on and I would like to test for
Hello again,
All these answers are client/server related and very informative, but
the original question is still in the open. In SQLite's case, let's
assume I want to make a wrapper which add some functionality and
simplifies some features. I create a cursor which contains a copy of
the data.
> > After that, it's of no use to keep the database open, so it closes it.
> > And sends the results obtained back to the client.
>
> Wow! This is the first I hear that. Wouldn't that be an expensive
> operation? (opening, closing, reopening...)
For an embedded database, such as SQLite, yes it
Hello George,
After that, it's of no use to keep the database open, so it closes it.
And sends the results obtained back to the client.
Wow! This is the first I hear that. Wouldn't that be an expensive
operation? (opening, closing, reopening...)
Thanks for your comments!
Regards,
-- Tito
On 19
Hello Tito,
>> Would you expect a cursor to live after is database has been closed?
Sure. Imagine a Client - Server scenario: the client makes a request (e.g. SELECT *
FROM Orders), request which is passed to a server. The server executes the sql and
obtains a recordset. After that, it's of no
8 matches
Mail list logo
