| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Richard Neill <rn214(at)richardneill(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, postgresql(at)richardneill(dot)org, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #8467: Slightly confusing pgcrypto example in docs |
| Date: | 2014-02-13 20:39:20 |
| Message-ID: | 20140213203920.GE32126@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Oct 10, 2013 at 08:42:14PM -0400, Bruce Momjian wrote:
> On Thu, Oct 10, 2013 at 08:32:32PM -0400, Bruce Momjian wrote:
> > > > How can the later entry not be MD5 hash?
> > >
> > > Because what you pass to the functions is 'md5', not 'md5 hash', which
> > > is what the new text appears to indicate.
> >
> > So if we revert, will it still be clear what is MD5 and what is MD5 hash?
>
> I mean, will it be clear what is MD5 crypt and what is MD5 hash?
I have made the attached doc change, which places "(hash)" outside of
the literal text block. You are right the literal blocks should match
what is passed.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| Attachment | Content-Type | Size |
|---|---|---|
| md5.diff | text/x-diff | 678 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-13 20:49:08 | Re: BUG #9210: PostgreSQL string store bug? not enforce check with correct characterSET/encoding |
| Previous Message | John R Pierce | 2014-02-13 20:13:28 | Re: Need Information |