"Stuart D. Gathman" <[EMAIL PROTECTED]> writes:
> As far as I can see from a quick glance, the key feature that is sacrificed
> to allow it to be fast and simple is multiple active transactions.
> (Plus, there is no GRANT/DENY or user or permission meta data tables.)
> This is perfect for a single user application. I like how it fully
> implements transaction processing and recovery for the single active
> transaction.
Gnucash doesn't need multiple active transactions... Also, SQLite
doesn't need grant/deny; that's accomplished via Unix File permissions
(although admittedly it provides access to the complete database,
whereas you might want to limit access to certain tables). However,
once you give the user write-permission to the file, any finer-grained
access control mechanism is really just a hurdle, providing a false
sense of security. Someone could still write to any portion of the
file. So grant/deny makes no sense for sqlite.
But yea, that's why we want to use it.. Now we just need to finish
the code. Any helpers?
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
