> I'm not so sure I like the inheritance of the "not null" properties of
> the DOMAIN.

IMO, there are two different things -->

The "based on" approach, which uses the same datatype as the
column referenced.

and

the real "domain" approach, which uses the datatype, null-ability
and check constraint (given that it's a "domain").

Both features would be a "very nice to have" when it comes to
developing stored procedures.



If you're creating "based on", why would that include null-ability?

Why not add a "not null" to parameters as an additional feature,
making sure they are being passed values upon calling the procedure?


Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com