Subject | Re: [ib-support] Master-Detail constraint checking |
---|---|
Author | Marcos Vinicius Dufloth |
Post date | 2003-04-28T11:48Z |
Yeh, I don't realize that. Other way to control this is create a boolean
field in master table to update after the last detail row is inserted,
then a trigger before update master table can look to this field. If
true, make validation reading all details rows and throwing an exception.
Dufloth.
Helen Borrie wrote:
*__________________________________________________________________*
*Marcos Vinicius Dufloth*
*ICQ#: 128291190*
*Current ICQ status:*
*(* *Work Tel#:* 54 522-3313
*+* *More ways to contact me * <http://wwp.icq.com/128291190>
*__________________________________________________________________*
[Non-text portions of this message have been removed]
field in master table to update after the last detail row is inserted,
then a trigger before update master table can look to this field. If
true, make validation reading all details rows and throwing an exception.
Dufloth.
Helen Borrie wrote:
> At 08:21 AM 28/04/2003 -0300, Dufloth wrote:--
> >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:
> >
> > > 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.
>
> Sure, for a banking sheet you would want to hold the transactions in
> "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
>
>
>
> *Yahoo! Groups Sponsor*
> <http://rd.yahoo.com/M=229633.3212141.4526654.2595810/D=egroupweb/S=1705115386:HM/A=1556779/R=0/*http://shop.store.yahoo.com/cgi-bin/clink?ftd2+shopping:dmad/M=229633.3212141.4526654.2595810/D=egroupweb/S=1705115386:HM/A=1556779/R=1/1051529810+http://us.rmi.yahoo.com/rmi/http://www.ftd.com/rmi-framed-url/http://www.ftd.com/yahoo36>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/>.
*__________________________________________________________________*
*Marcos Vinicius Dufloth*
*ICQ#: 128291190*
*Current ICQ status:*
*(* *Work Tel#:* 54 522-3313
*+* *More ways to contact me * <http://wwp.icq.com/128291190>
*__________________________________________________________________*
[Non-text portions of this message have been removed]