SQLite odd behavior

[william humphrey]

Peter

I will download a copy of your program and install it on that old machine
and see if there is any weird behavior though. I just went to your
lcsql.comwebsite and downloaded the 30 day trial. I wanted to look at
your program
anyway as it sounds interesting.

Bill

On Fri, May 11, 2012 at 2:50 PM, Peter Haworth <pete at lcsql.com> wrote:

> Weird indeed.  One possible explanation (except for the 3 months old thing)
> is that you are issuing a BEGIN statement, then doing some updates but not
> issuing a COMMIT statement when you're done.  Those updates will only be
> visible to the specific data connection within Livecode that made the
> updates, not any other database access programs.
>
> My SQLiteAdmin program uses Livecode database access routines almost
> exclusively and I haven't come across this behavior.
>
> Other than that, as Bob said, are you sure you are accessing the same copy
> of the database in all three programs?
>
> Sounds like you've moved on now but I can pretty much guarantee this is not
> an sqlite misbehavior.
>
>
> Pete
> lcSQL Software <http://www.lcsql.com>
>
>
>
> On Fri, May 11, 2012 at 10:42 AM, william humphrey <
> bill at bluewatermaritime.com> wrote:
>
> > In case this ever happens to someone else... I have a SQLite database
> that
> > I access with version 4.6.2 of livecode and now version 5.0. This
> Livecode
> > database is behaving like it has a secret section which can be written to
> > by LiveCode and read from by LiveCode but when you look at it with
> > SQLiteManager you don't see those changes (you also don't see those
> changes
> > when you look at it with vStudio).  Also, even more unpredictably,
> > sometimes you can write changes to the SQLite database which even
> LiveCode
> > in the same session can't see. You can add something to it with
> > SQLiteManager and that change is always visible in all three programs.
> Also
> > once I opened it up in LiveCode and it had rolled back to data three
> > month's old. This behavior is beyond me to figure out and since that is
> my
> > last stack that still uses SQLite I converted it to Valentina with the
> > vStudio application from Valentina that converts databases and now I'm
> > making many improvements in the stack which take advantage of Valentina's
> > features not the least of which is vServer.
> >
> > Anyway I'm not knowledgeable enough to figure out what's going on with
> > SQLite and I'm now going to stay away from SQLite as that was a pretty
> > scary data loss (of course I have back ups) in a working program in the
> > middle of a job. I'm also moving forward to LiveCode 5.5 which drops some
> > of the database query builder stuff I shouldn't have been using anyway.
> > Maybe the SQLite behavior had something to do with the Mac I was working
> on
> > version 10.6.8 so I upgraded that to  Lion. Since SQLite is basically
> just
> > a simple text file this behavior is possibly something to do with MacOS
> and
> > not LiveCode at all. I do my backups to drop box.
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
http://www.bluewatermaritime.com