Bug 411976 - Update the comment in mozIStorageService.idl to reflect recent SQLite changes. This is a comment change only - NPOTDB.

This commit is contained in:
sdwilsh@shawnwilsher.com 2008-01-25 10:18:15 -08:00
parent b17cd6a67e
commit 1777cc37e8

View File

@ -46,11 +46,6 @@ interface nsIFile;
* a service that can create storage connections (mozIStorageConnection) * a service that can create storage connections (mozIStorageConnection)
* to either a well-known profile database or to a specific database file. * to either a well-known profile database or to a specific database file.
* *
* The implementation of this service using sqlite with the async IO module
* must be created the first time on the main thread. If you want to use it
* from another thread, you should be sure you call getService from the main
* thread before accessing it from another thread.
*
* This is the only way to open a database connection. * This is the only way to open a database connection.
*/ */
[scriptable, uuid(a4a0cad9-e0da-4379-bee4-2feef3dddc7e)] [scriptable, uuid(a4a0cad9-e0da-4379-bee4-2feef3dddc7e)]
@ -84,10 +79,6 @@ interface mozIStorageService : nsISupports {
* a simple string compare to see if there is already a connection. Opening * a simple string compare to see if there is already a connection. Opening
* a connection to "Foo.sqlite" and "foo.sqlite" will CORRUPT YOUR DATABASE. * a connection to "Foo.sqlite" and "foo.sqlite" will CORRUPT YOUR DATABASE.
* *
* Opening connections from more than one thread to the same database will
* also CORRUPT YOUR DATABASE. All connections share the same sqlite cache,
* and the cache is not threadsafe.
*
* The connection object returned by this function is not threadsafe. You must * The connection object returned by this function is not threadsafe. You must
* use it only from the thread you created it from. * use it only from the thread you created it from.
* *