Re: bug with distinct?

Alfonso Peniche <alfonso@iteso.mx>

From: Peniche Lopez Alfonso Jose <alfonso@iteso.mx>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alfonso Peniche <alfonso@iteso.mx>, pgsql-general@postgresql.org
Date: 2001-02-10T17:11:14Z
Lists: pgsql-general
Quoting Tom Lane <tgl@sss.pgh.pa.us>:

> Alfonso Peniche <alfonso@iteso.mx> writes:
> >      SELECT distinct \'mod_type\' 
,currval(\'mytable_idmytable_seq\') from
> > mytable;
> > ERROR:  Unable to identify an ordering operator \'<\' 
for type \'unknown\'
> >  Use an explicit ordering operator or modify the 
query
>
> You need to give the literal an explicit type, eg,
>
>      SELECT distinct \'mod_type\'::text, 
currval(\'mytable_idmytable_seq\')
> from
>      mytable;
>
> 7.1 will default to assuming that you meant \'text\' in 
this scenario,
> but older releases are pickier.
>
> 			regards, tom lane
> 
Thanx, it woeks great now.

Cheers

---