| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types, constructors, and the type system |
| Date: | 2011-06-30 16:34:18 |
| Message-ID: | 1309451658.10707.141.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2011-06-29 at 10:15 -0700, David E. Wheeler wrote:
> On Jun 29, 2011, at 10:13 AM, Florian Pflug wrote:
>
> > Because there might be more than one range type for a
> > base type. Say there are two range types over text, one
> > with collation 'de_DE' and one with collation 'en_US'.
> > What would the type of
> > range('foo', 'foooo')
> > be?
>
> The one that corresponds to the current LC_COLLATE setting.
Then how do you get a text range that doesn't correspond to the
LC_COLLATE setting? Does that mean you couldn't dump/reload from a
system with one collation and get the same values in a system with a
different collation? That would be very strange.
Or, what about other types that just happen to have multiple useful
total orders?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2011-06-30 16:40:53 | Re: Range Types, constructors, and the type system |
| Previous Message | Jeff Davis | 2011-06-30 16:29:37 | Re: Range Types, constructors, and the type system |