to save or not to save objects

This is the place to post technical queries about SQL Yoga

Moderators: FourthWorld, heatherlaine, Klaus, robinmiller, trevordevore

Post Reply
trevordevore
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 1005
Joined: Sat Apr 08, 2006 3:06 pm
Location: Overland Park, Kansas
Contact:

to save or not to save objects

Post by trevordevore » Fri Oct 11, 2013 1:56 pm

[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
Trevor DeVore
ScreenSteps - https://www.screensteps.com

LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder

trevordevore
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 1005
Joined: Sat Apr 08, 2006 3:06 pm
Location: Overland Park, Kansas
Contact:

Re: to save or not to save objects

Post by trevordevore » Fri Oct 11, 2013 1:57 pm

Not that I can think of. You can read the schema in and create any additional relationship objects, etc. at runtime.
Trevor DeVore
ScreenSteps - https://www.screensteps.com

LiveCode Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode
LiveCode Builder Repos - https://github.com/search?q=user%3Atrevordevore+topic:livecode-builder

Post Reply

Return to “SQL Yoga”