On 2016/10/08 1:12 PM, Damien Sykes-Lindley wrote:
Hi Ryan,
I think there may have been some misunderstanding here. The
application is a local application and thus needs no server, at least
on the data side. But multiple people may have access to the same
machine. So while user control is needed elsewhere, that certainly
isn't on the local side. Just a simple password would do.
Sorry, I think there are some misunderstandings, perhaps our word
choices are unfortunate.
Saying "We don't need user control - A simple password will do" is much
like saying "We don't need a lock, a simple key-and-keyhole mechanism
would do". A password is the very essence of user access control. Unless
you lock the file (and in so doing impose user-access-control via the
O.S.) but that is just removing the issue one step. You need user access
control, even if very simple. There is no reason to not also use a
normal DB system locally - especially since you are already opting that
way for the other more complex stuff (if I understand you correct).
To go one further, SQLite is very geared towards programmed systems, you
seem to need more a script connector DB system, these other DB's were
made for your use case. (Note: SQlite can do very well here too, just
that it isn't necessarily better than the others for that interface, add
to that the user control issue and I really think you should consider
another solution).
Hope that was less misunderstandy :)
Ryan
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
