Page 10 of 10

Re: My First SQLite Project

Posted: Wed Sep 30, 2009 7:06 am
by Rathinagiri
Yes, that would be better. :)

Re: My First SQLite Project

Posted: Wed Sep 30, 2009 8:11 am
by sudip
Hi All,

I am back again (I was busy due to festival).

IMHO, you are talking about problem of LOST UPDATE and DATA INTEGRITY.

LOST UPDATE problem is usually solved by record locking. Here, with SQLite we may use programming technique, eg., making one particular field 0 or 1 (as Sqlite has no logical field).

For DATA INTEGRITY, AFIK, Sqlite has FOREIGN KEY facility, but to implement data integrity, we have to use Insert or Delete triggers.

Again, TRANSACTION facility of Sqlite will help 1) to maintain data integrity and 2) efficiency (speed).

I may be wrong, so please correct me if I am wrong :)

With best regards.

Sudip

Re: My First SQLite Project

Posted: Wed Sep 30, 2009 8:26 pm
by mol
IMHO, "magic fields" with 0 or 1 - lock/unlock record has big defect - when program crashes (or computer crashes - e.g. power loose) - record remains locked and special action for clenup of locks are required.
I remember that mechanism built in PROGEN.

Re: My First SQLite Project

Posted: Thu Oct 01, 2009 4:25 am
by sudip
Yes Marek,
You are correct.
So, in this case ATOMIC TRANSACTION facility of Sqlite may be helpful :)
With best regards.
Sudip