--- In IB-Architect@y..., "Ann W. Harrison" <aharrison@i...> wrote:

> At 10:52 AM 4/10/2001 +0000, m.tonies@u... wrote:
>
> >My guess is that for procedures and views, you could still save the
> >view/proc source in the RDB$VIEW_SOURCE and RDB$PROCEDURE_SOURCE

and

> >mark the view 'invalid' in the RDB$FLAGS field...
>
> Sounds like a good idea to me - I'd probably use the same inactive
> mechanism that triggers use. However, this is an ODS change
> and will make Firebird databases incompatible with InterBase since
> InterBase will not understand the new state. Hardly the end of
> the world.

Just had another look at the system tables...

Views have RDB$FLAGS in it's RDB$RELATIONS table
Procedures have no field for this
Triggers have RDB$FLAGS in it's RDB$TRIGGERS table

But I have no idea what these fields hold right now... Probably a new
field would be better. I don't have any insight into the core engine
whatsoever, can someone with knowledge about that think about the
idea and see if it's possible?

Can someone explain what both of these RDB$FLAGS fields actually hold
inside them?


Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."