db encryption and multiuser question

[Trevor DeVore]

On Feb 5, 2008, at 5:21 AM, Tiemo Hollmann TB wrote:

> 1. I have read a few times that you can't / should not use sqlite  
> for a
> multiuser environment, instead you should take a "bigger" db as  
> valentine.
> My question is, are there any hard facts to not use sqlite in a  
> multi user
> environment? What would happen if my customers would read my db with
> multiple users - just a little slow down or wouldn't it work at all?  
> Does
> this point affect only if you have write statements on the db or  
> also if you
> only have a read db?

<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.

> 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.

Regards,

-- 
Trevor DeVore
Blue Mango Learning Systems
www.bluemangolearning.com    -    www.screensteps.com