Hello,
I have a question regarding sqlite's behavior when auto commit is disabled.
I have two conflicting transactions, A & B, where A is started first.
B starts by executing some SELECT queries (which all succeed), then on
the first UPDATE I get SQLITE_BUSY (as A is holding a conflicting
lock). I
Hi,
I'm wondering if sqlite has something similar to MySQL's SQL_CALC_FOUND_ROWS.
I'm sorry if this topic has been discussed before, but I've searched the
archives and found no final decision made about it yet...
TIA,
Mahmoud Al Gammal
--
This message was sent from a MailNull anti-spa
What matters for me the most actually is how sqlite will behave in a
non-concurrent scenario in case NFS fails (the NFS mount is suddenly
unavailable for example). Can I still assume that the ACID properties are
maintained?
[EMAIL PROTECTED] writes:
> [EMAIL PROTECTED] wrote:
>> Hello,
>> I'm
Hello,
I'm considering using sqlite in a system where the database might be accessed
concurrently from several machines over NFS. I'm aware of locking issues & NFS
but I have a couple of questions:
- Could an NFS-level failure cause data inconsistency, or can sqlite handle
such errors?
- I'm us
4 matches
Mail list logo