Pavan wrote:
The idea is that at any point of time user1 should not access user2
details and vice-versa.
SQLite doesn't have a concept of access control so if you want to stop
user1 from seeing user2's data then you'll either have to use a database
that does provide access control or , as you suggest, provide a separate
file for each user and control access via OS permissions. In that case
you needn't worry too much about normalising the data and you might even
find that an SQL database is overkill.
Does it make sense conceptually and is it feasible technically ?
Only you can answer the former ;) If you need that access control and
want to use SQLite then I guess separate files is as good as you'll get.
You could provide your own access control mechanism to a single file but
that'll be more work.
Martin
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
