From: Andreas Pflug <Andreas.Pflug@web.de>
To: pgsql-performance@postgresql.org
Subject: SELECT DISTINCT is picky about constants
Date: Tue, 04 Feb 2003 13:15:46 +0100
Message-ID: <3E3FAEF2.5080302@web.de> (raw)
The query
SELECT DISTINCT keycol, 'constant' FROM myTable
or
SELECT DISTINCT keycol, NULL FROM myTable
will result in an error message (7.3.1)
Unable to identify an ordering operator '<' for type "unknown"
Use explicit ordering operator or modify query
If I use 'constant'::varchar or NULL::varchar everything's fine.
Unfortunately, this SELECT DISTINCT will appear quite often in my app.
I'd rather like PostgreSQL to use implicit type casting for such
constants. The final type chosen doesn't matter anyway and life would be
easier.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: Andreas.Pflug@web.de
Subject: Re: SELECT DISTINCT is picky about constants
In-Reply-To: <3E3FAEF2.5080302@web.de>
References: <3E3FAEF2.5080302@web.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox