Morning List, Another morning another question, what sort of facilities does SQLite provide for Loading from a read only storage location and then saving changes to a separate read/write storage unit? I know I can open a database file with a read only flag but how would I go about managing the changes to that database and storing them to a separate storage device? All I could think of is creating a separate read/write database on the read/write storage but short of duplicating tables between the two databases I can't think of a simple mechanism for organising the two tables so only the changes to the original read only table are stored out into the read/write table with out adding allot of data management logic on the code side.
I'd imagine there is some mechanism for dealing with this kind of storage layout if SQLite is used in embedded systems as the sort of storage arrangement I'm describing is fairly common but I'm unsure as to the terms to search in the documentation for as every product seems to use different terms for that sort of facility. Any help or pointers to the correct bit of documentation to look at would be most appreciated! Cheers, Daniel Brown "The best laid schemes o' mice an' men, gang aft agley" _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
