Re: What's the logical counterpart of the to_hex function? - Mailing list pgsql-general

From Michael Nolan
Subject Re: What's the logical counterpart of the to_hex function?
Date
Msg-id 4abad0eb0707170548l6df0081ci60cbc18821f3d505@mail.gmail.com
Whole thread Raw
In response to Re: What's the logical counterpart of the to_hex function?  (Steve Atkins <steve@blighty.com>)
List pgsql-general


On 7/16/07, Steve Atkins <steve@blighty.com> wrote:

On Jul 16, 2007, at 11:36 AM, Michael Nolan wrote:

> I have data (from an external source) which is in text format as a
> hex number (it's actually an IP address, but that's probably not
> relevant.)

It likely is relevant, as it means it's a 32 bit unsigned integer,
which isn't something postgresql supports. Depending on what you need
you might want to look at using 32 bit signed, with a 2^31 offset, 64
bit signed, inet or ip4 (which is on pgfoundry, not built-in).


Actually, since what I need are the 4 dotted tuples, all I really need is a simple way to convert a two byte hex field to an integer, it sounds like the exec is the preferred (though IMHO clumsy) method.

--
Mike Nolan

pgsql-general by date:

Previous
From: "ARTEAGA Jose"
Date:
Subject: Re: Limitations on 7.0.3?
Next
From: ann hedley
Date:
Subject: average/stddev on all values returned by a select distinct