| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
| Subject: | Re: New notices? |
| Date: | 1999-09-29 15:57:06 |
| Message-ID: | 37F236D2.B2A27832@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This was added to address the long-standing error reports of problems
> when addressing aliased and non-aliased columns in the same query. We
> don't issue an error, but go ahead and auto-create a from entry, very
> non-standard SQL:
> SELECT tab.* FROM tab t
> Tom Lane and I agreed we need to issue a NOTICE for this type of
> auto-FROM creation.
OK, but I may happily break it when implementing table and column
aliases for join syntax. Don't know yet what the ramifications will
be...
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 1999-09-29 16:28:28 | Re: [HACKERS] Re: TODO items |
| Previous Message | Zakkr | 1999-09-29 15:50:25 | Re: [HACKERS] string function |