Here is my situation and why SQLite doesn't seem to satisfy it.
It would be great to hear what some of the SQLite developers think about this.
* My Mac OS X program has a document file format of packages (which are nothing
but glorified directories). My database file is always inside of a package. So,
it can be assumed that all the extra files (such as -journal) will always move
with the main database file if the user moves the document (the package).
* The program runs in sandbox mode (a requirement for all programs on Apple's
Mac App Store), meaning that if a user moves a package, the program will gain
read/write access to the new path but LOSE read/write access to the old path.
This poses a problem:
* A user could move the file during a transaction, i.e., between _prepare_v2();
and _finalize();
It seems that SQLite needs support for this situation. Would you agree?
If so, the question is how. Maybe through callback functions requesting an
updated directory when needed? Or by internally following the changed path of
the main database file instead of storing it in memory at the outset?
Until then, I guess I just have to live with the risk of either an error or
data corruption when a user moves a document (a package).
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
