BDB corrupt

[Kurt J. Lidl]

On Wed, May 14, 2008 at 12:25:16AM -0700, Garrett Cooper wrote:
> Most of the complaints about other DBs is licensing related, but SQLite's 
> complaint was also the fact that the past stability record was a bit rocky.

One other thing to watch for in SQLite is the lack of atomicity
in updates.  It's not ACID, just like BDB 1.8x isn't ACID.

Without a write-ahead log, you cannot be sure that the data written
actually made it to stable storage, and as such, you cannot be sure
that your database didn't get corrupted when the process stops in a
non-optimal way.

I view SQLite as adding syntactic sugar to your data access language.

It doesn't give you real tranactions, it doesn't give you a write-ahead
log, it doesn't give you referential integrity.  Heck, the last time
I looked (admitted, a while ago), it didn't even enforce column type
checking on tables.  (Put this string in the INT column? No problem!)

-Kurt