After having worked with a variety of databases (db2/oracle/mssql)
A user/connection/transaction has a default name space/schema.
If an absolute path ie schema.sqlobject is not specified, the current
default schema is used.
You can use synonyms to point to a sql object in a different schema as a
default path within your own schema.
A recursive namespace system would be perfect ie
schema.schema.schema......sqlobject would allow for easier conversion from
one database system to another ie
create schema logical
create schema physical
create schema production
create schema development
create schema production.billingprocess
create schema development.billingprocess
create table production.billingprocess.invoices(etc)
the application/user would specify their default schema and can switch from
development to production just by switching their default schema.
It would also aid in future features such as attaching a remote database to
a schema and thus treating it as part of the primary database.
Regardless, you would need variables such as "current schema" to determine
where you are in the logical design tree.
If you are looking for DDL/DML specifications along with standard sql
extensions, I would suggest looking to the online IBM DB2 and Oracle
documentation.
On 25 January 2014 14:24, Simonov Denis <[email protected]> wrote:
> Adriano dos Santos Fernandes <[email protected]> писал(а) в своём письме
> Sat, 25 Jan 2014 18:41:40 +0400:
>
> >
> > I don't know. To answer this, I would need detailed spec of how schemas
> > will work in Firebird.
> >
> > Will it be user-based or not, how multiple schemas will interact, how
> > current no-schema objects will be supported, how the namespace will be
> > shared between main objects and schemas, how it be the prefix syntax.
> >
> > AFAIK, Oracle does not treat this outside the schema-handling. I think
> > it's much safer to think on this when designing schemas than adding
> > something now that may cause future problems.
> >
> >
>
> I do not like the scheme made in Oracle. User and the scheme does not
> have the same thing. I'm much closer to realization schemas PostgreSQL.
>
> As for use of the procedures of the same name, in the presence of schemas
> it certainly an output. However there will be a problem of homonymy of
> schemas and packets. However current situation should be reflected in
> Release Notes.
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
