Hi,

> >Domains aren't just about data types - they're Domains: that is, a
> >particular
> >datatype with/out a check constraint and not null constraint and even a
> >default value.
>
> What I see is to use get the data type from the Domain and not bother with
> the constraints.

But a Domain is a Domain is a Domain. If it comes to datatypes only, I think
the solution below is better.

I remember it was TABLENAME.COLUMNNAME%TYPE

>
> >In a stored procedure, what would a parameter or variable be when it is
> >defined as NOT NULL?!
> >
> >I'd rather have the same construct as Oracle:
> >
> >Declare a variable as: myvar %EMPLOYEE.EMPNO%
>
> This would be helpful too, especially for those fields that don't have a
> domain.

Yep.

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."