Subject | Re: [Firebird-Architect] Cross database queries: Requirements |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2007-08-09T18:02:17Z |
Vlad Horsun escreveu:
ones or new ones.
It should be a system view IMO...
AFAIR, Oracle stores only a timestamp of the original object, and the
timestamp is also in the original database.
If timestamp of object (in "client" and "server" databases of dblink)
are different, the procedure/trigger are compiled again when executed,
and if necessary invalidated.
Adriano
> Why ? To introduce external entities in local database we need to atI think is wrong to put external metadata in tables, be it the current
> least add some fields into existing RDB$xxx tables. This means that existing
> drivers and applications can't correctly query new RDB$xxx and must be
> upgraded : imagine two tables T in two different catalogs : X.T and Y.T
> (or T@X and T@Y) - existing drivers not know about catalogs and will think
> database have two tables T.
>
> To preserve compatibility we must not extend RDB$xxx and put
> external entities into some new tables
ones or new ones.
It should be a system view IMO...
AFAIR, Oracle stores only a timestamp of the original object, and the
timestamp is also in the original database.
If timestamp of object (in "client" and "server" databases of dblink)
are different, the procedure/trigger are compiled again when executed,
and if necessary invalidated.
Adriano