Thread: Inet and distinct bug or is it me? (v 6.5beta1)

Inet and distinct bug or is it me? (v 6.5beta1)

From
Aaron Holtz
Date:
Howdy all.

Running 6.5beta1 and am seeing an issue.  It appears to be with the 'inet'
type.  Running a 'distinct' select against a column doesn't always
provide the right data.  I can find no reason why I'm getting multiple
answers back.  Example:


db=> select distinct nasidentifier from table;
  nasidentifier
---------------
200.200.200.131
200.200.200.156
200.200.200.156
200.200.200.156
200.200.200.156
200.200.200.181
200.200.200.181
200.200.200.181
(8 rows)


I read some posts regarding issues with the inet type and nulls, hence
my upgrade to 6.5   Anyone know what could be causing this?  The same
process inserts the data into the db and inspecting a flat file of the
outputted data shows no indication that the entries are different.
Any thoughts or pointers would be appreciated.



--------------------------------------------------------------------------
Aaron Holtz
ComNet Inc.
UNIX Systems Specialist
Email:  aholtz@bright.net
"It's not broken, it just lacks duct tape."
--------------------------------------------------------------------------