Subject | Re: [Firebird-Architect] Extended field/domain DEFAULT usage |
---|---|
Author | Dmitry Yemanov |
Post date | 2006-01-05T07:28:11Z |
"Jim Starkey" <jas@...> wrote in message
news:<43BC21BF.3080804@...>...
and alike? :-)
My position is that we must ensure such databases are restorable first.
are very local and if the feature requesters are keen to either accept
constants/parameters only in DEFAULT UDFs or recover from unrestorable
backups, I have no objections.
Dmitry
news:<43BC21BF.3080804@...>...
>What about "DEFAULT MY_UDF((SELECT VAL FROM MY_PROC), GEN_ID(MY_GEN, 1))"
> Any, returning to the original topic, I don't see any problems with
> support UDFs in default value clauses for domains. Do you?
and alike? :-)
My position is that we must ensure such databases are restorable first.
> I'm already getting pressure to check the changeI'd rather prefer to see Vulcan Beta released. But given that the changes
> in Vulcan. Any comments?
are very local and if the feature requesters are keen to either accept
constants/parameters only in DEFAULT UDFs or recover from unrestorable
backups, I have no objections.
Dmitry