Subject | Re: Domains as data type in PSQL |
---|---|
Author | Alexander V.Nevsky |
Post date | 2003-08-08T08:54:21Z |
--- In firebird-support@yahoogroups.com, "Martijn Tonies"
<m.tonies@u...> wrote:
each other, depth and structure of nested calls can be rather
large and complicated. Remember now what a headach we have changing
type of parameters in low-level procedure, especially if this
parameters pass through significant part of the calls tree. To teach
server make this automatically is'nt simple task. Remember that
procedures are often called by triggers which should become invalid
too. And annoying "object in use"...
Perhaps discussed feature is really useful, (not sure, I don't use
domains at all) but IMHO we have more interesting fields for
developer's activity :)
Best regards, Alexander.
<m.tonies@u...> wrote:
> PARAM1 EMPLOYEE.EMPLOYEEDID%TYPEprocedures
>
> As a param datatype - this also helps a lot. And yes, these
> are compiled as well. But when the EMPLOYEE.EMPLOYEEIDautomatically
> column is changed, the procedure is flagged "invalid" and
> re-compiled on the first callMartijn, it is not so simply in real world - procedures often call
each other, depth and structure of nested calls can be rather
large and complicated. Remember now what a headach we have changing
type of parameters in low-level procedure, especially if this
parameters pass through significant part of the calls tree. To teach
server make this automatically is'nt simple task. Remember that
procedures are often called by triggers which should become invalid
too. And annoying "object in use"...
> or youThis is more realistic.
> can have a decent developer-UI that shows you the invalid procedures
> and let's you recompile/change them.
Perhaps discussed feature is really useful, (not sure, I don't use
domains at all) but IMHO we have more interesting fields for
developer's activity :)
Best regards, Alexander.