[fdo-internals] FDO RFC 16 - FDO Provider for SQLite

Traian Stanev traian.stanev at autodesk.com
Tue Mar 18 16:12:18 EDT 2008

SQLite is ACID (for some value of ACID). I'm not sure what's involved in supporting transactions properly, but feature commands (insert/update/select) will internally be done using transactions anyway. With insert, one pretty much has to batch lots of inserts into one transaction, because a write transaction in SQLite involves closing and reopening the file -- which is a very slow way to coordinate access. Anyway, it really depends on what the most often used access pattern would be for such an FDO provider. So I guess the answer is "yes, if necessary, we can have explicit transaction support"? Also, keep in mind that you can start a transaction at any time using the FDO SQL command, then go on and execute some other feature commands, and end it by a commit.


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Tuesday, March 18, 2008 3:55 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO RFC 16 - FDO Provider for SQLite


I think you may have missed addressing Mateusz' question about
transactions.  Considering that SQLite is (apparently) ACID, wouldn't it
make sense to support these?


-----Original Message-----
From: Traian Stanev
Subject: [fdo-internals] FDO RFC 16 - FDO Provider for SQLite

I think my reply to RFC 16 questions got sent to the bit bucket, so here
it is, again:
fdo-internals mailing list
fdo-internals at lists.osgeo.org

More information about the fdo-internals mailing list