Re: [sqlite] Using SQLite in an existing project flat-file save mechanism

"Lists Hammersley" <[EMAIL PROTECTED]> wrote: > On 6/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > If you want to preserve the traditional File/Open + File/Save > > semantics, you could create an in-memory SQLite database then > > copy the disk database to the in-memory database on File/Op

Re: [sqlite] Using SQLite in an existing project flat-file save mechanism

On 6/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: If you want to preserve the traditional File/Open + File/Save semantics, you could create an in-memory SQLite database then copy the disk database to the in-memory database on File/Open, and copy the other way on File/Save. Doesn't this re

Re: [sqlite] Using SQLite in an existing project flat-file save mechanism

"Lists Hammersley" <[EMAIL PROTECTED]> wrote: > > We have an existing application which stores data out to flat files. > We would like to use SQLite as the storage mechanism for column-like > data, other datatypes would remain in flat-files. However, there are a > few use cases which make it diff

[sqlite] Using SQLite in an existing project flat-file save mechanism

Hi, Could anyone advise on best practices for using SQLite as storage when used in an existing application which uses file-based project storage? We have an existing application which stores data out to flat files. We would like to use SQLite as the storage mechanism for column-like data, other