db encryption and multiuser question

[Lynn Fredricks]

> <http://sqlite.org/whentouse.html>
> 
> Scroll down to "Situations Where Another RDBMS May Work 
> Better" and look at "Client/Server Applications". If you have 
> many users trying to write to the database file then you 
> should probably look for a different solution. Multiple reads 
> won't corrupt your database though.

Obviously I have some other thoughts in mind when it comes to SQLite, but,
it was never designed to be a multi-user database. There is a lot going
under the hood of a database engine to support multiple users.

> > 2. What about encryption (just read Victoras answer). ... My
> > question: Is this because
> > I am not a db specialist and for any advanced "specialist" 
> it wouldn't 
> > be any problem to get my datas out of my db with structure 
> and "sence"
> > and
> > everybody should encrypt his data to avoid dumping or is it really 
> > "only" a question of securing private datas?
> 
> As Eric said your data is not safe as anyone could open the 
> database and take a peak or perform a dump of the data. You 
> can encrypt the data in Rev before storing in the database 
> and then decrypt it when pulling the data out but be aware 
> that you lose the ability to perform searches on that data 
> using SQL. I believe encryption at the database level is 
> really needed if you want to search the data.

Its with the encryption part that I believe Dr Hipp has found his way to pay
his bills. Since it is the freeist sort of open source (public domain), its
not like its impossible to create your own encryption system either if you
are able.

Although we do see SQLite as a sort of competitor, its refreshing that Dr
Hipp doesn't try to promote its use for every possible database solution.
There are many types of database applications that handle small amounts of
data and are local that, you wouldn't necessarily see the advantage of ANY
one system over the other, because the time/security considerations are so
narrow. If you shaved an additional 11% off of one .02 second operation on
your local computer, who's going to notice, right? :-) Now if its working
with 2 million records and that 11% is shaved off of each interaction with
the record, that's where you see the difference.

The database market is extemely mature; the upside is that it allows the
development of special systems that can deliver specific
features/performance in specific databases that will meet your needs rather
than just being stuck with just 1-2 players that YOU have to adapt to.
Imagine cross-platform development if the ONLY solution was Java ;-)

Best regards,

Lynn Fredricks
President
Paradigma Software
http://www.paradigmasoft.com

Valentina SQL Server: The Ultra-fast, Royalty Free Database Server