Hello,
I became acquainted to SQLite through its implementation in the
upcoming PHP version 5.0. As such, it is taking on much the same role
that MySQL used to in versions up to the current official release (still
in the 4.x range). As I understand it, one of the primary reasons is
MySQL's licensing being incompatible with PHP's, but other reasons for
the change appear to be that SQLite's typing is much better suited to
PHP's typeless (or more accurately dynamically typed) environment where
a variable easily takes the role of a string, integer or even Boolean
when appropriate.
Leaving aside the debate of the benefits of typeless v. strongly typed
environments, the only issues I have had with SQLite is in dealing with
secure data, and more recently the issues of multiple access to the data
at the same time.
Seeing some of the recent postings, I am driven to find out more about
this aspect.
Am I correct in assuming the SQLite has primarily been a client-only
tool, and has not had a big part to play in web server environments?
What kind of issues might one encounter if it is used in a read-write
web server environment, esp where transactions might be involved.
Should one use many separate databases/files?
What happens if one has hundreds of thousands of records in one or two
tables, and many people use the web page at the same time? I have seen
some discussions among the PHP5 doodlers of using SQLite as the DB of
choice for session management, where data is stored from one page view
to the next to keep the values of anything from a few text fields to
large database reports. Has anyone determined how SQLite would fair with
this kind of use, esp as compared to other DB engines?
Speaking to the first question, regarding security of data, aside from
some of the obvious, like putting the DB files out of the web document
tree, are there any ways to configure SQLite to keep the DB files in
some non-readable format? I had hoped to use an architecture where each
web application had a SQLite DB in the same folder for session and
storage of data useful only to that app, and to have a general SQLite DB
file elsewhere for all apps to use, but was somewhat startled when I
tried accessing the SQLite file directly in my browser and got almost
perfectly readable data dumped to my screen.... I was hoping that I
might have overlooked a configuration switch that would make the file
unreadable, but have not found this yet....
Sorry for dumpling more than one question in the same email.... But
thanks to anyone who might share the benefits of their experience.
SQLite, I'm finding, is becoming a great tool, better and easier to
use/configure than MySQL. I just want to make sure I use it in the
correct contexts....
--
Vania Smrkovski
http://www.pandorasdream.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
