Hi Mike, Can happen if you issue a BEGIN without a corresponding COMMIT or ROLLBACK, then issue another BEGIN. Also, if by some chance you're using an admin tool that has the db locked for some reason. I've never used an sqlite db over a network connection but I've read that locks don;t work very well in that environment because it uses the native OS file locking mechanisms which apparently are not implemented very well in some network layers.
Pete lcSQL Software <http://www.lcsql.com> On Thu, Aug 29, 2013 at 1:32 PM, Mike Kerner <mikeker...@roadrunner.com>wrote: > How the heck can a single-threaded environment like LC create this error? > > I have a series of queries that hit sqlite, followed by UPDATE x SET y = 0 > WHERE y = 1 which results in this error. > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
