Anstin, I am not using transactions (no BEGIN in my SQL queries), and I do close the the result set that updates the query. If this is not something that should normally happen, I guess that the next step would be for me to create a reproducible test case.
Alex On Nov 12, 2:55 pm, Austin <[EMAIL PROTECTED]> wrote: > Hi, > SQLite should work correctly in cases like this. It is possible that you > might have > an open transaction or something that prevent you from seeing the data > in the other places. > > Austin > > On Mon, Nov 10, 2008 at 12:33 PM, Alessandro Vernet <[EMAIL PROTECTED]>wrote: > > > > > > > I have a situation where I have multiple iframes accessing the same > > data in SQLite through the Gears API. JavaScript is running in one > > iframe and write to a table. Right after that, JavaScript in another > > iframe goes to read the data written to that table. I noticed that the > > read operation doesn't have access to the latest data when executed > > right after the write operation. > > > Is there a way to ensure that when updating data in SQLite, that > > update is available right away to other JavaScript running in other > > windows? > > > Alex
