Date: Fri, 11 Jun 2004 08:54:02 +0100
From: Stephen Quinney <stephen.quinney@computing-services.oxford.ac.uk>
To: Chris Gamache <cgg007@yahoo.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Converting integer to binary
Message-ID: <20040611075402.GA4887@computing-services.oxford.ac.uk>
References: <20040610182756.GA22247@wolff.to>
	<20040610202415.89117.qmail@web13804.mail.yahoo.com>
	<20040610222731.GA26006@wolff.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040610222731.GA26006@wolff.to>
User-Agent: Mutt/1.5.5.1+cvs20040105i

On Thu, Jun 10, 2004 at 05:27:31PM -0500, Bruno Wolff III wrote:
> On Thu, Jun 10, 2004 at 13:24:15 -0700,
>   Chris Gamache <cgg007@yahoo.com> wrote:
> 
> Following up on the cast to bit idea, he could do something like
> casting to bit(32). I don't think there is an easy way to get this
> cast to string, so it may not completely solve his problem, depending
> on what he was going to do with the binary representation. On teh other
> hand, for some things a bit field might be more useful than a string.
> 
> area=> select 6::bit(32);
>                bit
> ----------------------------------
>  00000000000000000000000000000110
> (1 row)

That would probably work for me in this case as I am interfacing to
postgresql via the Perl DBI layer. With perl reading out that field
would give me a string representation.

Thanks for the tips,

Stephen Quinney