Doh! Know the feeling. Well!
On Wed, Mar 21, 2012 at 2:38 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 21 Mar 2012, at 7:35pm, Adam DeVita <adev...@verifeye.com> wrote: > > > Sorry for false alarm. Please disregard this thread: > > > > Solution: make sure you quit everything and isolate the code. There is a > > subsequent write to the new record that made it appear as a problem, when > > it wasn't. > > We've all done it. Glad you sorted it out. > > Simon. > _______________________________________________ > 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
