I'm puzzled by this reference to sqlite being slow, I think the second time you've mentioned it. It's an "in memory" database and faster than probably any other SQL implementation. It does indeed have many settings that control cache, etc. As for "industrial strenght" (whatever that means), there are people using sqlite tables with millions of rows in them and not complaining about performance issues.
That's not to say the sqlite is the ideal sql db for all applications, far from it. Particularly in multi-user situations, it lacks a lot of features found in other SQL implementations. But I'd venture to claim that in a single user environment, you won't find a faster SQL db. If you have any objective evidence to the contrary, I'd love to hear it! Pete lcSQL Software <http://www.lcsql.com> On Tue, May 29, 2012 at 8:37 PM, Kay C Lan <lan.kc.macm...@gmail.com> wrote: > My personal opinion on why Lion can be sluggish and resource hungry is that > so much of it now has SQLite as it's backend which I know is slower than > other DBs out there. I also THINK (no actual hard evidence) that in some > cases people are requiring industrial strength performance out of it and it > just isn't set up for that. Other DBs have all sorts of settings for > memory, cache, VM etc, to maximise performance depending on the particular > type/size of data you are dealing with. I'm not sure if any such tweaks > occur to the OS X SQLite DBs. > _______________________________________________ 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
