Thanks for your answer Martijn. Your points are exactly the reason why I think such
feature would be so useful, plus the added value of preserving the modelled bussiness
logic.

Maybe this ain't the right place to ask, but it hasn't be done because of:

a) FB architecture makes it imposible without major reengineering.
b) I'm too naïve, such a feature isn't feasible (NP complete?)
c) There are other priorities
d) Such a feature is a BadThing[tm]

Regards,
Daniel Berstein.

On 7 Aug 2003 at 22:32, Martijn Tonies wrote:

> 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
>
>
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>