From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Open 7.3 items |
Date: | 2002-08-14 02:42:49 |
Message-ID: | 1029292969.2052.3.camel@rh72.home.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2002-08-14 at 06:00, Bruce Momjian wrote:
> Sean Chittenden wrote:
> > > Well, they aren't separate fields so you can't ORDER BY domain. The dot
> > > was used so it looks like a schema based on dbname.
IMHO it should look like an user in domain ;)
> > Sorry, I know it's a single field and that there is no split()
> > function (that I'm aware of), but that seems like such a small and
> > easy to fix problem that I personally place a higher value on the more
> > standard nomeclature and use of an @ sign. I understand the value of
> > . for schemas and whatnot, but isn't a user going to be in their own
> > schema to begin with? As for the order by, I've got a list of users
> > per "account" (sales account), so doing the order by is on two columns
> > and the pg_shadow table is generated periodically from our inhouse
> > tables. -sc
>
> I have no personal preference between period and @ or whatever. See if
> you can get some other votes for @ because most left @ when the ORDER BY
> idea came up from Marc.
I still like @ . And I posted code that could be put in the pg_user view
to split out domain you could ORDER BY.
> As for it being a special character, it really isn't because the code
> prepends the database name and a period. It doesn't look to see if
> there is a period in the already or anything.
-----------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-14 02:43:18 | Re: [SQL] 16 parameter limit |
Previous Message | Scott Shattuck | 2002-08-14 02:29:47 | Re: db partial dumping with pg_dump |