Re: temporal period type and select distinct gives equality error - Mailing list pgsql-general

From Jeff Davis
Subject Re: temporal period type and select distinct gives equality error
Date
Msg-id 1296066333.11513.364.camel@jdavis
Whole thread Raw
In response to Re: temporal period type and select distinct gives equality error  (Arturo Perez <arturo@pleeque.com>)
List pgsql-general
On Wed, 2011-01-26 at 09:27 -0500, Arturo Perez wrote:
> > and yet when I do a select distinct with a join I get
> >
> > QueryLogger - *** error.
> > org.postgresql.util.PSQLException: ERROR: could not identify an equality
> > operator for type period
> >
> > If I leave the period column out of the select list then it works fine.
> >
> > Did I install it wrong?  Or is something else going on?
> >
> > tia
> > arturo
>
> No suggestions from anyone?  Anyone out there? :-)

Sorry, I missed this the first time.

I have added support for this in the CVS repository, but have not
included it in the latest release. The thing that's missing from the
released files is a "btree opclass", which is what postgresql uses to
find the right equality operator for DISTINCT.

I am currently working on "range types" which is a patch that will
provide support for PERIOD, as well as many other range types, in core.
That will, of course, support everything you expect, including DISTINCT
on the range type.

We're currently in the middle of the final commit fest for 9.1. After
this is over (or perhaps earlier, if I can find the time), I'll do some
clean up of the existing pgsql-temporal PERIOD type, and do a release of
that.

Regards,
    Jeff Davis


pgsql-general by date:

Previous
From: MargaretGillon@chromalloy.com
Date:
Subject: Re: Install Pgadmin3 1.12 on ubuntu 10.4 lucid client without postgresql server install
Next
From: Steve Crawford
Date:
Subject: Re: Getting the name of the timezone, adjusted for daylight saving