| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Open issues for collations |
| Date: | 2011-04-18 19:52:47 |
| Message-ID: | 1303156367.14718.8.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2011-04-18 at 10:41 -0400, Tom Lane wrote:
> However, I've come across a new issue that maybe requires discussion:
> what collation should be associated with a multi-row VALUES in FROM?
> For instance, in
>
> SELECT ... FROM
> (VALUES (1, 'foo'), (2, 'bar' COLLATE "C")) v(a,b),
> ...
>
> what collation should be imputed to references to v.b?
>
> The way the code currently works is that the first row of the VALUES
> list is inspected to determine what collation to report
Hmm, I do see this on my list of things to address, so yes, it should be
fixed. I likely got stuck because it's pretty complicated.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2011-04-18 20:08:52 | ORDER BY 1 COLLATE |
| Previous Message | Peter Eisentraut | 2011-04-18 19:44:53 | Re: Typed table DDL loose ends |