From: | Arturo Perez <arturo(at)pleeque(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: temporal period type and select distinct gives equality error |
Date: | 2011-01-27 12:32:15 |
Message-ID: | arturo-5A594C.07321527012011@news.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In article <1296066333(dot)11513(dot)364(dot)camel(at)jdavis>,
Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> 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 thought I saw that in CVS but when I checked it out and installed it
the error did not go away.
Let me try that again. Do you think I'd need to reinstall the server
itself to insure the proper behavior?
tia,
arturo
From | Date | Subject | |
---|---|---|---|
Next Message | Girts Laudaks | 2011-01-27 12:52:58 | Dumpall without OID |
Previous Message | Sim Zacks | 2011-01-27 10:56:01 | Re: Queyring for columns which are exist in table. |