From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | t-ishii(at)sra(dot)co(dot)jp, tgl(at)sss(dot)pgh(dot)pa(dot)us, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] select + order by |
Date: | 1999-05-17 08:51:42 |
Message-ID: | m10jJ7e-000EBZC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > > > select usename as aaa from pg_user order by usename;
> > > > will produce 2 column names: "aaa" and "usename". Is this normal?
> > >
> > > No. I am not seeing it here with sources from 12 May. I am guessing
> > > this has something to do with Jan's recent fixes for group by/order by
> > > rewrites. Do you see it when you use a plain table, rather than a view?
> >
> > I see it with a plain table too.
>
> I just did a make clean, initdb, etc, and got:
>
> test=> select usename as aaa from pg_user order by usename;
> aaa
> --------
> postgres
> (1 row)
>
> Looks good to me.
Yes, latest changes require a clear, intidb due to changes in
the node out/read functions.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-05-17 09:02:46 | Re: [HACKERS] rules regression test |
Previous Message | Jan Wieck | 1999-05-17 08:27:26 | Re: [HACKERS] Misleading Error Message |