open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10064 Commits
38 Branches
669 Tags
732 MiB
Tag: Branch: Tree: 5af4855383
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5af4855383'
${ noResults }
postgres/contrib/pgcrypto/pgcrypto.sql.in

24 lines
560 B
Raw Normal View History Unescape

Hashing functions from Marko Kreen <marko@l-t.ee>
26 years ago
-- drop function digest(text, text);
-- drop function digest_exists(text);
I would like to do a interface change in pgcrypto. (Good timing, I know :)) At the moment the digest() function returns hexadecimal coded hash, but I want it to return pure binary. I have also included functions encode() and decode() which support 'base64' and 'hex' encodings, so if anyone needs digest() in hex he can do encode(digest(...), 'hex'). Main reason for it is "to do one thing and do it well" :) Another reason is if someone needs really lot of digesting, in the end he wants to store the binary not the hexadecimal result. It is really silly to convert it to hex then back to binary again. As I said if someone needs hex he can get it. Well, and the real reason that I am doing encrypt()/decrypt() functions and _they_ return binary. For testing I like to see it in hex occasionally, but it is really wrong to let them return hex. Only now it caught my eye that hex-coding in digest() is wrong. When doing digest() I thought about 'common case' but hacking with psql is probably _not_ the common case :) Marko Kreen
25 years ago
-- drop function encode(text, text);
-- drop function decode(text, text);
Hashing functions from Marko Kreen <marko@l-t.ee>
26 years ago
CREATE FUNCTION digest(text, text) RETURNS text
AS '@MODULE_FILENAME@',
Revise handling of oldstyle/newstyle functions per recent discussions in pghackers list. Support for oldstyle internal functions is gone (no longer needed, since conversion is complete) and pg_language entry 'internal' now implies newstyle call convention. pg_language entry 'newC' is gone; both old and newstyle dynamically loaded C functions are now called language 'C'. A newstyle function must be identified by an associated info routine. See src/backend/utils/fmgr/README.
25 years ago
'digest' LANGUAGE 'C';
Hashing functions from Marko Kreen <marko@l-t.ee>
26 years ago
CREATE FUNCTION digest_exists(text) RETURNS bool
AS '@MODULE_FILENAME@',
Revise handling of oldstyle/newstyle functions per recent discussions in pghackers list. Support for oldstyle internal functions is gone (no longer needed, since conversion is complete) and pg_language entry 'internal' now implies newstyle call convention. pg_language entry 'newC' is gone; both old and newstyle dynamically loaded C functions are now called language 'C'. A newstyle function must be identified by an associated info routine. See src/backend/utils/fmgr/README.
25 years ago
'digest_exists' LANGUAGE 'C';
Hashing functions from Marko Kreen <marko@l-t.ee>
26 years ago
I would like to do a interface change in pgcrypto. (Good timing, I know :)) At the moment the digest() function returns hexadecimal coded hash, but I want it to return pure binary. I have also included functions encode() and decode() which support 'base64' and 'hex' encodings, so if anyone needs digest() in hex he can do encode(digest(...), 'hex'). Main reason for it is "to do one thing and do it well" :) Another reason is if someone needs really lot of digesting, in the end he wants to store the binary not the hexadecimal result. It is really silly to convert it to hex then back to binary again. As I said if someone needs hex he can get it. Well, and the real reason that I am doing encrypt()/decrypt() functions and _they_ return binary. For testing I like to see it in hex occasionally, but it is really wrong to let them return hex. Only now it caught my eye that hex-coding in digest() is wrong. When doing digest() I thought about 'common case' but hacking with psql is probably _not_ the common case :) Marko Kreen
25 years ago
CREATE FUNCTION encode(text, text) RETURNS text
AS '@MODULE_FILENAME@',
'encode' LANGUAGE 'C';
CREATE FUNCTION decode(text, text) RETURNS text
AS '@MODULE_FILENAME@',
'decode' LANGUAGE 'C';