Hi,

> And when switching a nullable field to not-null there is NO adverse
> effect with existing table records containing nulls??

I believe you should make sure there are no NULLs available - but I
also think that if there is a default defined, it will be used for the
NULLs.

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

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."

> Regards,
> Andrew Ferguson
>
> --- In ib-support@y..., "Martijn Tonies" <m.tonies@u...> wrote:
> > Hi,
> >
> > WARNING!!
> >
> > > DELETE FROM RDB$RELATION_CONSTRAINTS
> > > WHERE
> > > (RDB$CONSTRAINT_TYPE = 'NOT NULL') AND
> > > (RDB$RELATION_NAME = 'TABLE_NAME') AND
> > > (RDB$CONSTRAINT_NAME = 'INTEG_7');
> >
> > 'INTEG_7' is the name of the existing constraint -- it can be named
> > differently!!!
> >
> > Make sure to look it up first!!
> >
> > Martijn Tonies
> > InterBase Workbench - the developer tool for InterBase and Firebird
> > http://www.interbaseworkbench.com
> >
> > Upscene Productions
> > http://www.upscene.com
> >
> > "This is an object-oriented system.
> > If we change anything, the users object."
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>