My thought is one per app, although it might work for multi-user apps as well.
The file sits in a file system path just like an Access DB or XML file.
You call it out via a file path.
Apparently Android, iPhone and HTML5 can all use SQLite for storage.
So if you create an Android or iPad app, you would essentially let each app have a SQLite DB instance for it's settings/localized data.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 3
date: Tue, 25 Jan 2011 08:27:34 -0600
from: Aaron Bartell <aaronbartell@xxxxxxxxx>
subject: Re: [WEB400] Anyone here using SQLite ?
The thing I haven't quite figured out is where an instance SQLite sits that would allow other scripts in different "contexts" (Java term) to access it.
Or is the idea to have many SQLite instances - a new one for each app?
I am curious about SQLite because I plan on making use of it in the near future on Android, so thanks for brining this up Richard! :-)
Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com
midrange.com
