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

Re: Binary data type with other output method

From: imad <immaad(at)gmail(dot)com>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Binary data type with other output method
Date: 2007-12-25 17:12:23
Message-ID: 1f30b80c0712250912q178e725eha365f9bc6cd56b44@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
If you reduce your code you will have to leverage the bool data type.

Why dont you provide a cast, I dont see an overhead in typbyval datatypes.


On Dec 25, 2007 9:10 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> Andreas 'ads' Scherbaum wrote:
> > Hello all,
> >
> > i'm in the need to create a boolean datatype which returns an integer
> > instead of the usual 't'/'f'. Before anyone starts to point me at
> > casts: it's a lot overhead to cast some hundred occurances beside the
> > source of trouble, if you forget one.
> >
> >
> >
> Do you really need a new datatype or just to change the output behaviour
> of the inbuilt type? That should be quite easy to do in just a few lines
> of code.
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>


--Imad

In response to

Responses

pgsql-hackers by date

Next:From: Gokulakannan SomasundaramDate: 2007-12-25 18:04:38
Subject: Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)
Previous:From: Usama DarDate: 2007-12-25 16:57:42
Subject: Re: timetz range check issue

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