"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Richard Huxton <dev(at)archonet(dot)com> 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 particular case differently.
And do what? The only information you have is that all the inputs are
of unknown type. You do not get to look at context, because the type
resolution algorithm has to work bottom-up in expressions.
regards, tom lane
In response to
pgsql-general by date
|Next:||From: Scott Marlowe||Date: 2006-11-29 19:39:55|
|Subject: Re: Postgresql data integrity during RAID10 drive rebuild|
|Previous:||From: Kevin Grittner||Date: 2006-11-29 19:32:54|
|Subject: Re: coalesce with all nulls can only be assigned to|