>> I dont particularly want domain constraints applied to domains
>> used in triggers and SPs. I just want the data-type, for two
>> reasons...
>>
>> - Its convenient
>>
>> - It helps procedures to self-document - for example; here
>> is a variable and its type (domain) tells you that this
>> char(1) (or smallint or whatever) is used as a boolean.

> I proposed the same more than two years ago, but the reaction
> from the audience wasn't encouraging.
> :-)

I can just imagine that, if this was provided, we would get
inundated with complaints that the constraints and defaults were
not applied (despite the problems this would cause in all but
specialised situations).

But I would still like it. As far as possible I currently write
all my triggers and procedure variables with a little comment
telling me what domain they belong to. Then, when I need to
change a domain, I can search through my scripts and discover
all the places that used that domain and update accordingly.
Its an ugly, nasty, horrible process on very big scripts, but
it seems the only way to keep things in sync at the moment.

Being able to use the domains directly would save me lots of
typing, and the pain of finding out that I missed some trigger
or procedure.

--
Geoff Worboys
Telesis Computing