| Subject | Re: [firebird-support] Domains and Why they wont work for I/O params in stored procs. |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-03-02T00:13:17Z |
At 11:01 PM 1/03/2005 +0000, you wrote:
the (many) ways it differs from a data type is that it can be
changed. When a domain definition is changed, the changes are propagated
to all of the column definitions that use them.
A PSQL module is a compiled object, not a definition - hence, domain
changes could not be propagated to a PSQL module without a huge amount of
(currently unsupported) conflict resolution and subsystem activity in the
database.
./heLen
>I am a new FB user and I am not able to use defined domains in theTrue.
>IN/OUT params of stored procs.
>Are there any plans to change this behaviour ?No, not soon.
>The way I thought aboutA domain is not a data type, it is a packaged column definition. One of
>the usage for Domains, is you define a type (and behaviour) once and
>refer to it in other places(just like #define in C/C++). That way you
>only need to change it in one place if the defenition changes.
>
>Anyone have any idea on why it was done this way ?
the (many) ways it differs from a data type is that it can be
changed. When a domain definition is changed, the changes are propagated
to all of the column definitions that use them.
A PSQL module is a compiled object, not a definition - hence, domain
changes could not be propagated to a PSQL module without a huge amount of
(currently unsupported) conflict resolution and subsystem activity in the
database.
./heLen