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

Re: case when evaluating else condition anyway?

From: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: case when evaluating else condition anyway?
Date: 2008-11-26 15:17:40
Message-ID: 20081126161740.749580d4@dawn.webthatworks.it (view raw or flat)
Thread:
Lists: pgsql-general
On Wed, 26 Nov 2008 14:18:44 +0000
Sam Mason <sam(at)samason(dot)me(dot)uk> wrote:

> On Wed, Nov 26, 2008 at 02:53:07PM +0100, Ivan Sergio Borgonovo
> wrote:
> > case when ''=extinput then null else extinput::timestamp end
> 
> I'd tend to use nullif(extinput,'')::timestamp for this sort of

Thanks it was on the top of my fingers... BTW it was a substituted
literal ala printf before anything was piped to postgresql, so
actually postgresql would receive something as the examples below.

Still why does the else condition get evaluated anyway when at least
one of the "when" condition is true?

> thing. It's not going to do anything much different from what
> you're doing, but may end up evaluating "extinput" less which may
> be a good thing.
> 
> > Is there any cleaner functional way that doesn't involve prepared
> > statement etc... since the whole exercise is caused by an
> > null-impaired DB API (aka MySQLish).
> 
> As Tom said, maybe if you could send a larger example it would
> help.

as a more self contained example:

select case when ''='' then null else ''::timestamp end;

vs.

select nullif('','')::timestamp;

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it


In response to

Responses

pgsql-general by date

Next:From: Tom LaneDate: 2008-11-26 15:20:49
Subject: Re: Problem with langage encoding
Previous:From: Ronald VyhmeisterDate: 2008-11-26 15:10:04
Subject: Re: Problem with langage encoding

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