jose isaias cabrera <[EMAIL PROTECTED]>
wrote:
Perhaps, this should be the case. It would not be so hard to keep a
table of connections that are attached or open with a table.
You don't want an otherwise read-only connection have to write to the
database. This will harm concurrency.
Well, only one connection can modify a particular database file at
the same time. It doesn't matter if you open the file directly, or
attach it to an existing connection. If two processes attempt the
modifying
operation at the same time, one of them will proceed and the other
will be locked out.
Is there a way of telling the DB to UPDATE records after the actual
connection has completed its processing? Something like UPDATE queue?
I'm not sure I understand the question. Update records after which of
possibly multiple connections has completed its processing?
Igor Tandetnik
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
