On 7/7/05, Vladimir Vukicevic <[EMAIL PROTECTED]> wrote:
On Wed, 2005-07-06 at 08:40 -0700, Scott Baker wrote:
> Looks like Firefox is gearing up to store some of its information in
> SQLite? Does anyone know anything more about this?
>
> http://gemal.dk/blog/2005/07/06/mozilla_firefox_bookmarks_in_for_a_rewrite/
We'll be using sqlite, but not directly -- there is a layer currently
called mozStorage which is basically a XPCOM/C++ wrapper around sqlite
that I've written, along with convenience wrappers for working with
mozStorage within JavaScript. (For example, statement parameters can
be assigned via "stmt.params.paramName = 'value'" and simple
statements can just be called as functions, as in "stmt(param1,
param2);")
Good morning Vlad,
I've finished a Firefox extension using mozIStorage. After looking at the
documentation again I find it's got a data corruption issue waiting to happen.
The docs say:
" How to corrupt your database
* Open the database from an external program while it is open in
Mozilla. Our caching breaks the normal file-locking in sqlite that
allows this to be done safely. "
Which is exactly what I need to do. I'm capturing information about downloaded
files and making it accessible to programs outside the browser. There's also the
possibility of other programs writing to this database. Is there any
way to turn off
the caching and revert to regular sqlite locking on a per connection basis?
Otherwise I'm going to have to write my own xpcom wrapper around sqlite
and that really seems a waste since the code is already present.
Thanks
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
