Hi,

> >
> > I have a database on IB 6.0.2 and created a view with the WITH CHECK
> OPTION
> > clause. I noticed appearing two triggers, obviously
> checking the clause :)
> >
> > When I did the same yesterday on IB 6.5, these triggers
> didn't appear as
> > 'normal' triggers, but had a RDB$SYSTEM_FLAG value of 5 (VIEW CHECK
> OPTION).
> > IB 6.0.2 doesn't know this type in RDB$TYPES.
> >
> > FB RC2 restored the database with the two 'normal'
> triggers. Dropping the
> > view and re-creating it created the two triggers with type
> 5 - is this one
> > of the bugfixes for FB and taken into IB 6.5?
>
> Please double check which engine you used. :-)
> I wasn't aware that IB6.5 would do the same than Firebird.
> Hope you really ran the IB6.5 executable.

I believe I did - I have IB 6.5 on my own box and Firebird RC2
on a remote one...

>I assigned numbers to the special
> triggers to
> avoid supposing things based on names like CHECK_ and INTEG_
> because you can
> create those names with normal DDL. However, for
> compatibilty, we still
> check names.

Yes, I noticed 5 for VIEW CHECK and so on...

I also checked with IB 6.0.2 (what we're running here) and it
behaves like IB 6.0 - it keeps RDB$SYSTEM_FLAG NULL for auto-
created triggers, right?

The trigger numbers are a great addition -- it let's you
really see the difference! Boy, had (we) I had to go to great
length to know if a trigger was really a check constraint...

Thanks!

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com


[Non-text portions of this message have been removed]