Re: boolean <=> text explicit casts

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: boolean <=> text explicit casts
Date: 2007-05-30 19:02:04
Message-ID: 1180551724.6648.90.camel@goldbach
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Mon, 2007-28-05 at 15:38 -0400, Tom Lane wrote:
> More generally, I'm really hoping to get rid of bespoke text<->whatever
> cast functions in favor of using datatypes' I/O functions. To what
> extent can we make the boolean I/O functions serve for this? It seems
> relatively painless on the input side --- just allow whitespace --- but
> I suppose we can't change boolout's historical result of "t"/"f" without
> causing problems.

Attached is a revised version of this patch that modifies boolin() to
ignore leading and trailing whitespace. This makes text => boolean
trivial, but boolean => text is still distinct from boolout().

Barring any objections, I'll apply this later today or tomorrow.

-Neil

Attachment Content-Type Size
bool_text_cast-3.patch text/x-patch 9.1 KB

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Jeff Davis 2007-05-30 19:08:41 Re: Seq scans status update
Previous Message Tom Lane 2007-05-30 18:39:46 Re: WIP: 2nd-generation buffer ring patch