Subject | RE: [Firebird-Architect] Statement Cache [was: User name SYSDBA] |
---|---|
Author | Leyne, Sean |
Post date | 2005-08-31T02:10:06Z |
Jim,
One of the feature which Oracle has that I think would be very
beneficial to Firebird is the ability to change the definition of any
object (say a table) via at any time. Instead of verifying that the
dependent objects are not in use, Oracle proceeds with the change but
marks each of the active dependent objects as invalid, thus requiring
the object to be recompile.
This approach would go a long way to simplifying schema maintenance.
As such, the ability to mark on object as invalid would be "a good
thing".
Sean
> There is never any need to invalidate compiled statements.Are you sure about that?
One of the feature which Oracle has that I think would be very
beneficial to Firebird is the ability to change the definition of any
object (say a table) via at any time. Instead of verifying that the
dependent objects are not in use, Oracle proceeds with the change but
marks each of the active dependent objects as invalid, thus requiring
the object to be recompile.
This approach would go a long way to simplifying schema maintenance.
As such, the ability to mark on object as invalid would be "a good
thing".
Sean