On 10 Feb 2012, at 5:32pm, Kit wrote: > 2012/2/10 Sreekumar TP <sreekumar...@gmail.com>: >> Though the example of $ is very intuitive, I am not suggesting that we >> drop one of the transaction and block the database forever (as it is >> happening now). Instead, it could be serialized such that two $100 >> transactions are committed to the db. > > A situation in which I read from the database first and then changes > the data tells me that they are wrong questions. It is such a problem > to insert SELECT into UPDATE or INSERT?
Why do you need to do a SELECT at all ? Can you present us with a simple example of your situation ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users