Eduardo <[EMAIL PROTECTED]> wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
first sqlite3_step succeeds, an implicit transaction is started
(I assume there are no explicit transactions i
At 14:27 06/11/2005, you wrote:
Eduardo <[EMAIL PROTECTED]> wrote:
Isn't better lock the database while a transaction that can make a
SQLITE_SCHEMA error, as is done with writes? A change in database is
always a change. Also that way you don't waste time in rerunning the
affected transactions.
Ulrich Telle wrote:
In case of a SELECT statement the situation is still more complex. The
SCHEMA error could happen after reading several result rows. If you would
then redo the query automatically it would start from scratch delivering the
already read rows again. If your application code gath
I guess I have the same attitude as an old Main Framer I tried to sell a
Datapoint Arc Net long, long ago. His summation of the presentation
was, " I have enough damn trouble with one CPU. Why would I want a
whole network full of them!" I can barely keep one release of a
database running, why wo
4 matches
Mail list logo
