Bad time external representation '' - Mailing list pgsql-sql

From Heiko
Subject Bad time external representation ''
Date
Msg-id 000601c1f767$17b34000$010aa8c0@heiko1
Whole thread Raw
Responses Re: Bad time external representation ''  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-sql
hi,

currently upgraded SuSE linux 7.0 to 8.0 including an upgrade from postgres
7.0 to 7.2.
almost everything went very well, all the data intact, very peachy. only one
seemingly stupid problem:
queries like 'select case when a.dtmstart is null then '' else a.dtmstart
end from a;' where 'dtmstart' is a time-field result in a 'bad time external
representation ''' - error. (tried various casting tricks, none worked).

it works fine if i just leave the entire 'case when' - section out; if i
remember correctly, i put the section in because otherwise i got explicit
'null' values in my application; this does not happen anymore, so the
'select case' workaround has become superfluous.

for various reasons it would be a major pain in the butt for me, however, to
change the sql syntax in my applications; i would either have to produce and
control twice the amount of versions or change my interface so that it
catches the 'null's that 7.0 produces. is there a way to make postgres 7.2.
accept my old 'case when'-queries? and on a logical basis: why should a
'case when' expect one explicit data-type? shouldn't it theoretically be
possible to use a 'case when' also to hand back different types depending on
whether the condition comes true or not? or am i overlooking something basic
(would not be entirely untypical of me :-)

thanks a lot for any help,

h. jakubzik



pgsql-sql by date:

Previous
From: "Rajesh Kumar Mallah."
Date:
Subject: core file found...
Next
From: Andrew Perrin
Date:
Subject: Re: escaping arrays in perl dbi