Quoting Phil Longstaff <[EMAIL PROTECTED]>:
> On Fri, 2006-27-10 at 11:58 -0400, Derek Atkins wrote:
>
>> I'm not sure what you mean by "cascade of DELETE operations".
>> I think we CAN depend on the DB supporting transactions, but it
>> might depend on what level of TXN support we want/need.
>
> With foreign keys, you can specify what should happen if a row in
> another table is changed when the first table refers to the second one.
> For example, we could set it up that since a transaction split refers to
> the account it is in (foreign key), if an account is deleted, all splits
> referring to that account are also deleted. Or, if the account GUID is
> changed, all splits referring to that account will have the foreign key
> GUID changed.
Well, GnuCash already handles these cases. It wont let you delete an
account if there are splits in it. Also, GUIDs cannot change, so
that's never going to happen, either.
I.e., gnucash itself already performs all these referential tests for
you; the DB just needs to be a pure data store.
> Phil
-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
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
