On Mon, 10 Mar 2008, Tom Lane wrote:
I'd be inclined to leave the mapping alone and just insert a warning
(or hard error) for inputs outside the range -1 to 1.
Here's a patch that errors out for out of range values.
Kris JurkaIndex: doc/src/sgml/func.sgml
==
Kris Jurka <[EMAIL PROTECTED]> writes:
> On Wed, 11 Apr 2007, Tom Lane wrote:
>> It's not really possible to use it "incorrectly", AFAICS. Any value you
>> might pass to it will result in a specific new seed value. Nowhere is
>> there any guarantee of what the mapping is, and it's obviously
>> im
Thank you, you're right and I should have none !
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Heikki Linnakangas
Envoyé : dimanche 9 mars 2008 15:24
À : Yann ROBIN
Cc : pgsql-bugs@postgresql.org
Objet : Re: [BUGS] BUG #4021: UUID NULL and not equal que
Yann ROBIN wrote:
So my conclusion is that the NOT EQUAL operator doesn't match how it should
the NULL value field.
Is it a bug or a wanted behavior ?
It's normal behavior, required by SQL standard, and not specific to
UUIDs. See also
http://www.postgresql.org/docs/8.3/interactive/functions-c
-Message d'origine-
>It seems to be a client encoding problem. What is your client_encoding?
>A common problem is a mismatch between client_encoding and the terminal
>or application encoding.
I've tried different encoding, I always get the same error.
As I said, I've got the same exact d
The following bug has been logged online:
Bug reference: 4021
Logged by: Yann ROBIN
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0 build 140
Operating system: Windows XP SP2
Description:UUID NULL and not equal query failed
Details:
Hi,
I've tried to do
