From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | Joe Conway <joseph(dot)conway(at)home(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgcryto strangeness... |
Date: | 2002-01-05 21:39:31 |
Message-ID: | 13214.1010266771@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Sean Chittenden <sean(at)chittenden(dot)org> writes:
> Yeah, it does... but it also tells me I'm SOL for 7.1.3 even though
> pgcrypto comes with a DECODE() function (only supports 'hex' and
> 'base64'). Any other ideas? <:~) -sc
So, create yourself another function. In pgcrypto.sql.in I see
CREATE FUNCTION digest(bytea, text) RETURNS bytea
AS 'MODULE_PATHNAME',
'pg_digest' LANGUAGE 'C';
You could add
CREATE FUNCTION digest(text, text) RETURNS bytea
AS 'MODULE_PATHNAME',
'pg_digest' LANGUAGE 'C';
which should work fine since the internal representation of text isn't
really different from that of bytea.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brent Verner | 2002-01-05 21:41:01 | Re: Some interesting results from tweaking spinlocks |
Previous Message | Joe Conway | 2002-01-05 21:12:01 | Re: pgcryto strangeness... |
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2002-01-05 21:52:40 | Re: pgcryto strangeness... |
Previous Message | Joe Conway | 2002-01-05 21:12:01 | Re: pgcryto strangeness... |