Re: Obsolete functions istrue, isfalse, etc.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Obsolete functions istrue, isfalse, etc.
Date: 2008-10-04 22:39:49
Message-ID: 16904.1223159989@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> istrue
> isfalse
> isnottrue
> isnotfalse

> Should we remove those now? I suppose there is a slight chance that
> 10 year old dumps might contain references to them? But it is easy to
> reimplement them in user-space should anyone need them.

Of course the other side of the coin is that it's not costing us
anything noticeable to leave them there. But I have no strong objection
to removing 'em.

If we are going to get rid of them, I'd say we should also nuke
nullvalue() and nonnullvalue().

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2008-10-04 23:21:51 Re: Common Table Expressions applied; some issues remain
Previous Message Tom Lane 2008-10-04 22:22:23 Common Table Expressions applied; some issues remain