db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: Problem with CHECK constraints
Date Thu, 13 Nov 2008 13:10:35 GMT
Thanks for the sleuthing, Dag. This would be answer (C) in my original mail:

C) The current schema when the CREATE TABLE statement was issued?


Dag H. Wanvik wrote:
> Hi,
> I found this in section 4.27.2 Characteristics of SQL-invoked routines:
>> If a <routine invocation> is contained in a <query expression> of a
>> view, a check constraint, or an assertion, the <triggered action> of a
>         ****************
>> trigger, or in an <SQL-invoked routine>, then the subject routine for
>> that invocation is determined at the time the view is created, the
>> check constraint is defined, the assertion is created, the trigger is
>> created, or the SQL-invoked routine is created.
> So it would appear that Derby's present behavior is wrong.
> Thanks,
> Dag

View raw message