Skip site navigation (1) Skip section navigation (2)

Re: Range Types, constructors, and the type system

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Jeff Davis <pgsql(at)j-davis(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:59:43
Message-ID: A9F84B6D-9EA2-4EEF-8A8E-00132CE97B5F@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jun 30, 2011, at 9:34 AM, Jeff Davis wrote:

> Then how do you get a text range that doesn't correspond to the
> LC_COLLATE setting?

You cast it.

> 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.

No, pg_dump should always explicitly cast things. But there should be a reasonable default behavior if I'm in psql and don't cast.

> Or, what about other types that just happen to have multiple useful
> total orders?

Cast where you need it explicit, and have a reasonable default when it's not cast.

Best,

David



In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2011-06-30 17:00:51
Subject: Re: time-delayed standbys
Previous:From: David E. WheelerDate: 2011-06-30 16:58:42
Subject: Re: Range Types, constructors, and the type system

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group