> In my last post I mentioned that I updated my programs so that I can > execute an arbitrary query or update, thus eliminating the need to use > the sqlite command line utility. There really is only one program > accessing the database now.
Sorry, I've missed this detail. In this case you are safe indeed. Pavel On Thu, Jun 17, 2010 at 9:00 AM, Odekirk, Shawn <shawn.odek...@intelligrated.com> wrote: >>> I am not using BEGIN IMMEDIATE, just BEGIN, but I don't think it is a >>> problem in my case, since now there really is just one program > accessing >>> the database. >> >>Did you forget the message this thread was started from? The sqlite3 >>command line utility is a second program, so this could be a problem. >> >>Pavel > > Thank you for taking the time to respond. > No, I did not forget the message this thread was started from. I am the > one who started the thread. > In my last post I mentioned that I updated my programs so that I can > execute an arbitrary query or update, thus eliminating the need to use > the sqlite command line utility. There really is only one program > accessing the database now. > Please let me know if you still think that BEGIN IMMEDIATE is something > I should be using. > I am a newbie to sqlite and welcome any advice or suggestions. > > Thanks, > Shawn > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
