Horton

Re: contrib/pgcrypto functions not IMMUTABLE?

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marko Kreen <marko@l-t.ee>
Cc: Michael Fuhr <mike@fuhr.org>, Russell Smith <mr-russ@pws.com.au>, pgsql-hackers@postgresql.org
Date: 2005-07-03T16:02:38Z
Lists: 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