Hi Magnus,

If I were you, I would not rely on behaviour which should not exist
according to the documentation. In stead, I prefer defensive coding,
which would mean in your case:

a) Put in appropriate DML statements in the view triggers;
b) Assign the default values in code in corresponding table triggers.

Best wishes,
Marco


semprolbat wrote:

> Marco,
>
> > This implies that the validation error on the second statement is
> not
> > a bug. In stead, the fact that your first statement works at all
> (when
> > the trigger is in place) should be considered as an undocumented
> > feature. ("Works as programmed" was an answer we once received from
> a
> > technology vendor; "works as designed" would mean there is a
> design.)
>
> Well, I certainly hope they will stick with the current behaviour, as
> my whole database is based on views with triggers.... Too bad the
> default field value-thing does not work though.
>
>
>
>
> *Yahoo! Groups Sponsor*
> ADVERTISEMENT
> <http://rd.yahoo.com/M=246920.2960106.4328965.2848452/D=egroupweb/S=1705115386:HM/A=1481659/R=0/*http://www.gotomypc.com/u/tr/yh/cpm/grp/300_yh1/g22lp?Target=mm/g22lp.tmpl>
>
>
> 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/>.

--
-------------------------------------
-- Marco Bommeljé
-- Bommeljé Crompvoets en partners bv
-- W: www.bcp-software.nl
-- E: mbommelj@...
-- T: +31 (0)30 2428369
-------------------------------------