From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject:
Date: 2006-05-19 23:53:10
Message-ID: c2d9e70e0605191653ra0a14cdo87975a74584f8a9f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

suppose we have something like this:

upd_views=# create table tabla1 (col1 point);
CREATE TABLE
upd_views=# insert into tabla1 values ('3,2');
INSERT 0 1
upd_views=# insert into tabla1 values ('2,2');
INSERT 0 1
upd_views=# insert into tabla1 values ('3,2');
INSERT 0 1

then, this select will give an error:

upd_views=# select col1, count(*) from tabla1 group by col1;
ERROR: could not identify an ordering operator for type point
HINT: Use an explicit ordering operator or modify the query.
upd_views=#

i guess this is related to:
http://archives.postgresql.org/pgsql-hackers/2003-08/msg00809.php

so, what happened with this idea? there is another way to automagicaly
identify an "equality operator" for datatypes like 'point'?

as you said in the message linked above that is because postgres ask
for the operator name...

--
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-05-20 00:19:48 Re: [HACKERS] [OT] MySQL is bad, but THIS bad?
Previous Message Alvaro Herrera 2006-05-19 23:45:42 Re: text_position worst case runtime