| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <Thomas(dot)G(dot)Lockhart(at)jpl(dot)nasa(dot)gov>, Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Almost there on column aliases |
| Date: | 2000-02-16 15:48:32 |
| Message-ID: | 38AAC6D0.2B0AB8C@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >> BTW, the rule regress test is presently failing because I modified
> >> ruleutils.c to dump the Attr list if it is not null, rather than
> >> only if the refname is different from the relname:
I'm currently (2000-02-16 15:40 GMT) seeing the rules test
blank-filling the "bpchar" fields. Do you see that?
> > istm that the column aliases (rte->ref->attrs) should not be written out
> > if the table alias (rte->ref->relname) is not written.
> Hmm. If it's not possible to specify column aliases without specifying
> a table-name alias, then that's OK ... but I thought table aliases were
> optional.
I've just looked it up in the Date book: table aliases are optional in
general, but column aliases require a table alias. The bnf looks like
table [ [ AS ] range-variable [ ( column-commalist ) ] ]
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2000-02-16 15:57:03 | Re: [HACKERS] Postgres meets InterBase (ZDNet) |
| Previous Message | Tom Lane | 2000-02-16 15:43:35 | Re: [HACKERS] Solution for LIMIT cost estimation |