Thread: inet datatype

inet datatype

From
Joseph Shraibman
Date:
Is there any reason in particular that the inet type isn't returned by
the jdbc driver as an java.net.InetAddress ?


Re: inet datatype

From
Oliver Jowett
Date:
On Wed, Dec 03, 2003 at 09:12:36PM -0500, Joseph Shraibman wrote:
> Is there any reason in particular that the inet type isn't returned by
> the jdbc driver as an java.net.InetAddress ?

InetAddress doesn't store netmask information.

-O

Re: inet datatype

From
Joseph Shraibman
Date:
Oliver Jowett wrote:
> On Wed, Dec 03, 2003 at 09:12:36PM -0500, Joseph Shraibman wrote:
>
>>Is there any reason in particular that the inet type isn't returned by
>>the jdbc driver as an java.net.InetAddress ?
>
>
> InetAddress doesn't store netmask information.
>
> -O
... and the alternative is... ?  I say just return the InetAddress, and
if someone wants the netmask they'll have to call getString() and parse
it themselves.  Doing nothing is not an option.


Re: inet datatype

From
Oliver Jowett
Date:
On Wed, Dec 03, 2003 at 10:14:50PM -0500, Joseph Shraibman wrote:
> Oliver Jowett wrote:
> >On Wed, Dec 03, 2003 at 09:12:36PM -0500, Joseph Shraibman wrote:
> >
> >>Is there any reason in particular that the inet type isn't returned by
> >>the jdbc driver as an java.net.InetAddress ?
> >
> >
> >InetAddress doesn't store netmask information.
> >
> >-O
> ... and the alternative is... ?

Build an appropriate class that stores the whole type, along the lines of
what's done for the geometric types. That class can implement a
toInetAddress() method if needed.

> I say just return the InetAddress, and
> if someone wants the netmask they'll have to call getString() and parse
> it themselves.  Doing nothing is not an option.

I don't think doing a lossy conversion by default is a good solution.

-O