Subject | Re: [Firebird-Architect] Schemas |
---|---|
Author | Dmitry Yemanov |
Post date | 2009-09-24T10:41:55Z |
Claudio Valderrama C. wrote:
allows you to query their inter-related data without any cross-db
facilities. This is a common approach e.g. when your company has ERP and
HR software from different vendors but you need some combined reporting
or implement easy data migration between them.
Also, you may want to put a few really independent but similarly managed
databases together (into different schemas) in order to administer them
easier (as a single physical entity).
I think this is a useful feature, also considering its presence in the
SQL specification (IIRC, it's the only feature from the core subset of
SQL-92 which we don't support), but I wouldn't call it really urgent
(although I'd assign it a higher priority than longer-then-31-char
identifiers-but-without-schemas :-).
Dmitry
>Having a few partially and/or implicitly dependent databases together
> Now, who sees schemas as an urgent need and why?
allows you to query their inter-related data without any cross-db
facilities. This is a common approach e.g. when your company has ERP and
HR software from different vendors but you need some combined reporting
or implement easy data migration between them.
Also, you may want to put a few really independent but similarly managed
databases together (into different schemas) in order to administer them
easier (as a single physical entity).
I think this is a useful feature, also considering its presence in the
SQL specification (IIRC, it's the only feature from the core subset of
SQL-92 which we don't support), but I wouldn't call it really urgent
(although I'd assign it a higher priority than longer-then-31-char
identifiers-but-without-schemas :-).
Dmitry