Subject | Re[2]: [firebird-support] Domains in SP |
---|---|
Author | Nando Dessena |
Post date | 2004-04-05T08:26:16Z |
Helen,
HB> The problem is, SPs are compiled. What happens if you could use a domain to
HB> define an argument or a variable and the domain specification
HB> changed? It's no good saying "but my domain spec isn't going to
HB> change". Many people do change them.
this is "easily" solved by invalidating or recompiling the SP.
AFAIU the real problem is that noone was able to provide a complete
description of the semantics needed to support every characteristic of
domains (like check constraints) when passing them as parameters.
Everybody wants to be able to define a parameter using the same _type_
as <something else>, be it a domain or a table column (Oracle has a
ugly but effective syntax to do that). Nobody can tell what should we
do with other attributes of domains.
That's where we are currently, AFAIU.
Ciao
--
Nando mailto:nandod@...
HB> The problem is, SPs are compiled. What happens if you could use a domain to
HB> define an argument or a variable and the domain specification
HB> changed? It's no good saying "but my domain spec isn't going to
HB> change". Many people do change them.
this is "easily" solved by invalidating or recompiling the SP.
AFAIU the real problem is that noone was able to provide a complete
description of the semantics needed to support every characteristic of
domains (like check constraints) when passing them as parameters.
Everybody wants to be able to define a parameter using the same _type_
as <something else>, be it a domain or a table column (Oracle has a
ugly but effective syntax to do that). Nobody can tell what should we
do with other attributes of domains.
That's where we are currently, AFAIU.
Ciao
--
Nando mailto:nandod@...