Subject RE: [Firebird-Architect] Metadata locking policy and caching
Author Paul Hope
I hang around on this group only half understanding most of what is
discussed - but this latest discussion is ringing alarm bells ...

To us it is absolutely essential that the ability to update metadata on a
live database remains at least as felexible as it is now (FB1.5 SS). There
is no way we can ask users to shut down while we make minor updates. We've
been doing this without problem for the past 13 years.

Last year we tried to implement CS on a site that could really benefit from
it, however when we discovered we could not update a procedure until anyone
who had touched it that day had logged out, we had to revert to SS.

Pleeeese dont remove this valuable functionaltiy ;-)

Regards
Paul Hope
>
> 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
>