Subject | RE: [ib-support] Detecting a Not NULL field in a select |
---|---|
Author | Ignacio J. Ortega |
Post date | 2002-11-22T23:42:55Z |
Paul,
I'm a stupid.., this turn to be a bug in FB 1.0 !!! i ever interpreted
this behaviour as a bug in ib 5.6, and no is FB that does not issue
XSQLVAR with (sqltype & 1 != 1) when the selected relation is a pure
table, everything is ok, but it fails with views, every field in a
updatable view has "Nulls" allowed!!! ib 5.6 doesnt behaves this way, it
honors the the state of the not null constraint in the sqltype field..
I'm about to report that finding to Firebird-devel..
Saludos,
Ignacio J. Ortega
> If this doesn't work - let me know. I hate it when documenation isHistory rewrite like in 1984 ( G. Orwell )..
> _really_ wrong.
>
I'm a stupid.., this turn to be a bug in FB 1.0 !!! i ever interpreted
this behaviour as a bug in ib 5.6, and no is FB that does not issue
XSQLVAR with (sqltype & 1 != 1) when the selected relation is a pure
table, everything is ok, but it fails with views, every field in a
updatable view has "Nulls" allowed!!! ib 5.6 doesnt behaves this way, it
honors the the state of the not null constraint in the sqltype field..
I'm about to report that finding to Firebird-devel..
Saludos,
Ignacio J. Ortega