From: | Peniche Lopez Alfonso Jose <alfonso(at)iteso(dot)mx> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alfonso Peniche <alfonso(at)iteso(dot)mx>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: bug with distinct? |
Date: | 2001-02-10 17:11:14 |
Message-ID: | 200102101711.f1AHBEO55768@iteso.mx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Alfonso Peniche <alfonso(at)iteso(dot)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
---
From | Date | Subject | |
---|---|---|---|
Next Message | Anand Raman | 2001-02-10 17:16:11 | locking problem with JDBC (suspicion) |
Previous Message | Tom Lane | 2001-02-10 17:01:08 | Re: 7.1 installation problem |