diff options
| author | Peter Eisentraut | 2018-02-07 02:59:40 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2018-02-22 16:34:54 +0000 |
| commit | 0db2fc98cdf4135f9dcfa3740db6f2548682fe7e (patch) | |
| tree | db5021d09855116210d3d0fe877c188483586a67 | |
| parent | 10cfce34c0fe20d2caed5750bbc5c315c0e4cc63 (diff) | |
Update gratuitous use of MD5 in documentation
It seems some people are bothered by the outdated MD5 appearing in
example code. So replace it with more modern alternatives or by
a different example function.
Reported-by: Jon Wolski <jonwolski@gmail.com>
| -rw-r--r-- | doc/src/sgml/citext.sgml | 10 | ||||
| -rw-r--r-- | doc/src/sgml/sepgsql.sgml | 2 |
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/citext.sgml b/doc/src/sgml/citext.sgml index 82251de8529..b1fe7101b20 100644 --- a/doc/src/sgml/citext.sgml +++ b/doc/src/sgml/citext.sgml @@ -80,11 +80,11 @@ CREATE TABLE users ( pass TEXT NOT NULL ); -INSERT INTO users VALUES ( 'larry', md5(random()::text) ); -INSERT INTO users VALUES ( 'Tom', md5(random()::text) ); -INSERT INTO users VALUES ( 'Damian', md5(random()::text) ); -INSERT INTO users VALUES ( 'NEAL', md5(random()::text) ); -INSERT INTO users VALUES ( 'Bjørn', md5(random()::text) ); +INSERT INTO users VALUES ( 'larry', sha256(random()::text::bytea) ); +INSERT INTO users VALUES ( 'Tom', sha256(random()::text::bytea) ); +INSERT INTO users VALUES ( 'Damian', sha256(random()::text::bytea) ); +INSERT INTO users VALUES ( 'NEAL', sha256(random()::text::bytea) ); +INSERT INTO users VALUES ( 'Bjørn', sha256(random()::text::bytea) ); SELECT * FROM users WHERE nick = 'Larry'; </programlisting> diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml index 273efc6e271..f8c99e1b002 100644 --- a/doc/src/sgml/sepgsql.sgml +++ b/doc/src/sgml/sepgsql.sgml @@ -370,7 +370,7 @@ $ sudo semodule -r sepgsql-regtest <para> For example, consider: <synopsis> -UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100; +UPDATE t1 SET x = 2, y = func1(y) WHERE z = 100; </synopsis> Here, <literal>db_column:update</literal> will be checked for |