Re: Nested Schemata, in a Standard-Compliant Way?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Nested Schemata, in a Standard-Compliant Way?
Date: 2021-09-28 13:36:20
Message-ID: 2834126.1632836180@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com> writes:
> So, for example, I'd like to be able to say something like this:

> SELECT * FROM /projects/contacts/people;

I looked into this many years ago. (The reason why pg_namespace is called
that and not pg_schema is exactly that I thought it might someday include
sub-schemas.) I don't think it's possible to do it without huge ambiguity
problems, unless you introduce some separator other than dot, as indeed
you suggest here. But I also don't think that using some other separator
is a good idea. There's not that much free punctuation available (unless
you want to step outside core ASCII, which'd bring its own problems).
Pretty much every character that isn't otherwise nailed down is allowed
as an operator character, meaning that redefining it is very likely to
break somebody's application or extension. We had huge problems even
with taking over the => digraph, never mind single characters.

In the end the functionality-versus-problems ratio is just not going
to be very good.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message rob stone 2021-09-28 14:13:03 Re: Nested Schemata, in a Standard-Compliant Way?
Previous Message Raymond Brinzer 2021-09-28 13:24:35 Nested Schemata, in a Standard-Compliant Way?