On 15 Aug 2009, at 9:58am, Sebastian Arcus wrote: > I've just noticed another interesting thing. A read operation after a > write on same table (like a SELECT statement after an INSERT) works > perfectly fine - instantly. Which is bizarre, as I would have > expected a > write to keep a much longer lock on the table then a read. So it's > only > writes after reads that causes the lock.
Would it be possible to put the SQL commands into a text file, use the command-line utility to execute the text file, and time how long it takes ? Since the command-line utility uses the bare sqlite function library and very little extra code, this would tell you whether the delay is being caused by the SQLite library on down, or some level above the SQLite library. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
