From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Fernando Nasser" <fnasser(at)redhat(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: What's the CURRENT schema ? |
Date: | 2002-04-06 09:14:45 |
Message-ID: | EKEJJICOHDIEMGPNIFIJGEFJHGAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Fernando Nasser
>
> Hiroshi Inoue wrote:
> >
> > > We can't do that. Accordingly to the SQL if you are user HIROSHI
> > > and write "SELECT * FROM a;" the table is actually "HIROSHI.a".
> > >
> > > This must work for people who are using SQL-schemas in their databases
> > > or we would have a non-conforming implementation of SCHEMAS
> (would make
> > > the whole exercise pointless IMO).
> >
> > Schema name isn't necessarily a user id since SQL-92
> > though SQL-86 and SQL-89 had and probably Oracle still
> > has the limitation. As far as I see PostgreSQL's schema
> > support wouldn't have the limitation. Probably I wouldn't
> > create the schema HIROSHI using PostgreSQL. When
> > I used Oracle I really disliked the limitation.
> >
>
> You misunderstood what I've said. You may have how many schemas
> you please. But you will have to refer to their objects specifying
> the schema name explicitly. The only cases where you can omit the
> schema name are (accordingly to the SQL'99 standard):
Please tell me where's the description in SQL99 ?
I wasn't able to find it unfortunately.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-04-06 09:14:53 | Re: timeout implementation issues |
Previous Message | Tom Lane | 2002-04-06 07:27:18 | RFC: Restructuring pg_aggregate |