Re: contrib/pgcrypto functions not IMMUTABLE? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: contrib/pgcrypto functions not IMMUTABLE?
Date
Msg-id 4646.1120406558@sss.pgh.pa.us
Whole thread Raw
In response to Re: contrib/pgcrypto functions not IMMUTABLE?  (Marko Kreen <marko@l-t.ee>)
Responses Re: contrib/pgcrypto functions not IMMUTABLE?  (Marko Kreen <marko@l-t.ee>)
List pgsql-hackers
Marko Kreen <marko@l-t.ee> writes:
> And if you decide to do it, please make them all STRICT too,
> _except_ encrypt/decrypt functions.  Thats an additional change
> I have in the air for pgcrypto.sql.in.

> As for the encrypt/decrypt functions, I am increasingly
> favouring throwing error in case of NULL arguments.

That doesn't seem like a good idea at all.  Why shouldn't an encryptable
value be NULL?  I think you should just make 'em strict.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Checkpoint cost, looks like it is WAL/CRC
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] Dbsize backend integration