Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Kevin Grittner
>>> On Wed, Nov 29, 2006 at 1:32 PM, in message <[EMAIL PROTECTED]>, "Kevin Grittner" <[EMAIL PROTECTED]> wrote: On Wed, Nov 29, 2006 at 1:09 PM, in message > <[EMAIL PROTECTED]>, > Richard Huxton wrote: > >> Another option I can think of: Spot the case where all values in the >> coales

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Martijn van Oosterhout
On Wed, Nov 29, 2006 at 01:45:09PM -0600, Kevin Grittner wrote: > > And do what? The only information you have is that all the inputs > > are of unknown type. > > I know this is naive, but, what is the type information of the bare > null? Could that be used? A null can be of any type, string,

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Richard Huxton
Kevin Grittner wrote: On Wed, Nov 29, 2006 at 1:38 PM, in message <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote: "Kevin Grittner" <[EMAIL PROTECTED]> writes: Richard Huxton wrote: It's the coalesce that has the problem, not the insert. The coalesce is deciding that it's working

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Kevin Grittner
>>> On Wed, Nov 29, 2006 at 1:38 PM, in message <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote: > "Kevin Grittner" <[EMAIL PROTECTED]> writes: >> Richard Huxton wrote: >>> It's the coalesce that has the problem, not the insert. The coalesce is >>> deciding that it's working on text, a

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > Richard Huxton wrote: >> It's the coalesce that has the problem, not the insert. The coalesce is >> deciding that it's working on text, and so returns text. > It seems like maybe it would be worth overloading the coalesce method > to handle this p

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Kevin Grittner
>>> On Wed, Nov 29, 2006 at 1:09 PM, in message <[EMAIL PROTECTED]>, Richard Huxton wrote: > Kevin Grittner wrote: >> Tom Lane <[EMAIL PROTECTED]> wrote: >> We never do assume that a text literal is a valid date. I won't bore >> you with all the details unless you ask for them, but we're runni

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Richard Huxton
Kevin Grittner wrote: Tom Lane <[EMAIL PROTECTED]> wrote: We never do assume that a text literal is a valid date. I won't bore you with all the details unless you ask for them, but we're running on Java and generating literals based on the object type passed to a low level method. A null has n

Re: [GENERAL] coalesce with all nulls can only be assigned to

2006-11-29 Thread Kevin Grittner
>>> On Wed, Nov 29, 2006 at 12:15 PM, in message <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote: > "Kevin Grittner" <[EMAIL PROTECTED]> writes: >> [ "coalesce(null, null)" yields type TEXT ] > > Well, it has to yield *something*. You'd get the same result from > "coalesce('2006- 11- 29'

Re: [GENERAL] coalesce with all nulls can only be assigned to text

2006-11-29 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > [ "coalesce(null, null)" yields type TEXT ] Well, it has to yield *something*. You'd get the same result from "coalesce('2006-11-29', '2006-11-30')" ... you might think this looks like dates, but it's just some untyped literals and the parser chooses