Page 1 of 1

to save or not to save objects

Posted: Fri Oct 11, 2013 1:56 pm
by trevordevore
[This post is an archive from old SQL Yoga forums]

I am saving ebooks as sqlite files. The schema of these files is the same.

I also have a book.db that identifies which bookfile is which and of course has a different schema.

is there anything to be gained by saving the schemas to these two types of databases in my app over simply reading them in each time I open the app from the files present.

James

Re: to save or not to save objects

Posted: Fri Oct 11, 2013 1:57 pm
by trevordevore
Not that I can think of. You can read the schema in and create any additional relationship objects, etc. at runtime.