| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: \crosstabview fixes |
| Date: | 2016-04-14 09:47:10 |
| Message-ID: | 20160414094710.GD11804@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Daniel Verite 2016-04-14 <bc3a2e99-5030-4466-a248-98c5e9841205(at)mm>
> I don't quite see how to work around that, short of simply
> removing the possibility of addressing columns by their
> numbers. Which maybe is a bit sad for the end user, I'm not
> sure, but ISTM that's a logical consequence of abandoning
> the dedicated parser for columns.
That would be bad news, given that \crosstabview is meant for
interactive use where these number shortcuts are much more likely to
be used than in proper production SQL code. Be it only for ease of
typing, or for the case where the columns are just called ?column?.
If there's no way out, what about changing it the other way, i.e.
breaking the case where the column is named by a number? That seems
much less of a problem in practice.
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2016-04-14 10:05:39 | Re: Problems with huge_pages and IBM Power8 |
| Previous Message | Daniel Verite | 2016-04-14 09:41:20 | Re: \crosstabview fixes |