eWobbuh wrote:
For a database that is write once, read mostly, you probably wouldn't
have a lot of trouble, If I were doing it, I'd try to have most of the
sorting and other manipulations done in regular RAM or on the hard
drive to minimize repeated changes on the stick itself.
The idea is to read the database, make some changes and once in a while i
write the database to the usbstick. But how can i do the manipulations in
the RAM?
Leave it to Sqlite by doing it in a transaction. Ideally you would want
the journal files to be on your hard disk to get minimum read/write cycles.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
