Subject | Re: [Firebird-Architect] Metadata locking policy and caching |
---|---|
Author | Paul Beach |
Post date | 2008-08-06T07:42:07Z |
Adreano,
I think we are all aware of the issue re.
"We generally see users complaining about old procedure and triggers
versions running even in SS. We point them that this is documented in
IB6 docs."
As you correctly point out it has been documented for a log time.
At the moment reading this thread I feel that you are using
"a sledgehammer to crack a nut" - if the phrase doesn't make sense I
can explain it.
And I would suggest that your valuable time would be better spent working on other
issues in the engine.
Alex's comment:
"Please take into an account that this is VERY SERIOUS change in firebird
behaviour - since interbase days metadata modification was possible in
parallel with use of that objects. I'm sure that it will create a wave of
problems for our users not smaller than ones related with changes like
SQL-standard "NOT IN" or inability to use BLOBs in "SELECT DISTINCT". I will
be very happy to see a solution of MT-safe, clear, simple to program, etc.
metadata cache. But I do not like when it breaks logic and features which
existed for years."
Is something I wholeheartedly agree with.
Regards
Paul Beach
Tel (France): +33 (0) 2 47 58 30 43
Mob (France): +33 (0) 6 79 24 32 32
I think we are all aware of the issue re.
"We generally see users complaining about old procedure and triggers
versions running even in SS. We point them that this is documented in
IB6 docs."
As you correctly point out it has been documented for a log time.
At the moment reading this thread I feel that you are using
"a sledgehammer to crack a nut" - if the phrase doesn't make sense I
can explain it.
And I would suggest that your valuable time would be better spent working on other
issues in the engine.
Alex's comment:
"Please take into an account that this is VERY SERIOUS change in firebird
behaviour - since interbase days metadata modification was possible in
parallel with use of that objects. I'm sure that it will create a wave of
problems for our users not smaller than ones related with changes like
SQL-standard "NOT IN" or inability to use BLOBs in "SELECT DISTINCT". I will
be very happy to see a solution of MT-safe, clear, simple to program, etc.
metadata cache. But I do not like when it breaks logic and features which
existed for years."
Is something I wholeheartedly agree with.
Regards
Paul Beach
Tel (France): +33 (0) 2 47 58 30 43
Mob (France): +33 (0) 6 79 24 32 32