Subject | Re: [ib-support] Master-Detail constraint checking |
---|---|
Author | Helen Borrie |
Post date | 2003-04-28T11:35:28Z |
At 08:21 AM 28/04/2003 -0300, Dufloth wrote:
executes after the new record version has been created/updated and always
inside an uncommitted transaction.
"waystation" table, keyed in such a way that the SP inputs will identify
and target them; but the principle is the same, isn't it? Implement the
rules in procedural code on the server, not in xyz client applications...?
heLen
>This is the case to have an before commit trigger, don't?All triggers (Before and After) are "before commit". An After XXX trigger
executes after the new record version has been created/updated and always
inside an uncommitted transaction.
>Jason Chapman (JAC2) wrote:Sure, for a banking sheet you would want to hold the transactions in
>
> > Helen,
> >
> > I can't really see how you can do this for N-way accounting transactions.
> > e.g. a banking sheet may have 200 credits and 1 balancing debit on it.
> >
> > Personally I have in the past used temporary posting tables with an SP to
> > post into the main table, the SP can then validate prior to posting in the
> > actual nominal ledger. There is only 1 temporary table, it can hold many
> > TX's and you tell it which TX you want to post into the ledger. It checks
> > and posts or barf's.
"waystation" table, keyed in such a way that the SP inputs will identify
and target them; but the principle is the same, isn't it? Implement the
rules in procedural code on the server, not in xyz client applications...?
heLen