Hi Daniel,

> Is there any (good) reason why a domain can't be used as the datatype of

stored

> procedure parameters?
>
> It makes little sense to me to use a domain for columns definition but

have to refer to

> the underlaying datatype when coding stored procedures.

This has been requested... But:

A domain can have a CHECK constraint.

A domain can be defined as NOT NULL.

A domain can have a default (yes, this would be useful).

I guess this is why it hasn't been implemented yet.


btw, if you was to use Database Workbench to create your
stored procedures, you would be able to select a domain
when creating a parameter, and Database Workbench would
copy the raw datatype. Just as a shortcut.


With regards,

Martijn Tonies
Database Workbench - the developer tool for InterBase & Firebird
Upscene Productions
http://www.upscene.com