> I'm quite interested in hearing people's reasoning for going the blob route, > when you have a perfectly good "database" format for "blobs" already (various > filesystems).
Three technical reasons for me personally: * Can include blob operations as part of atomic transactions. * In SQLite, my blobs won't be corrupted if the machine loses power the way they (probably) will be if I write my own code to access the file-system. * Don't have to invent my own scheme for mapping from database entry to blob file, nor my own cross platform And the claim that it's less work to program that way. Better question IMO: What are peoples reasons for calling open() when you could just as easily call sqlite3_open()? :) > > -- > > D. Richard Hipp <[EMAIL PROTECTED]> > > > > > > --------------------------------------------------------------------------- > >-- To unsubscribe, send email to [EMAIL PROTECTED] > > --------------------------------------------------------------------------- > >-- > > > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
