Hi,

At August 7, 2004, 17:12, Aage Johansen wrote:

> Jacqui Caren wrote:

>> ...
>>
>> Even better, something similar to oracle
>>
>> declare variable pID MYTABLE.PID%TYPE;
>>
>> Eliminates the possibility that you get the domain wrong.
>>


> If you then change the domain definition you would "invalidate" the procedure.
> This has been discussed (on the firebird-devel list?), but I don't remember
> whether any action on this was agreed upon.

I think the action for now, is status quo.

Probably because there would be some work to be done before, this
could be implemented. For starters, if changing an SP's parameter's
domain, the SPs and Triggers that depend on that SP will have to be
marked as invalid and recompiled. But, this mechanism isn't
implemented yet, already it would be useful in other circumstances.
The other question where everybody didn't seem to agree on, was: do
you take into consideration the constraints found in the domain, or
simply the datatype?

Also, for these changes to take place immediately, there can only be
one user connected, otherwise those changes will have to be deferred
to the first occasion that they can be done(possibly only when there
is no connections, or all objects involved are no longer in use), or
simply get the error "object in use" and force the user to try again
later.

This is just my 2 cents.

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)