Re: BUG #8467: Slightly confusing pgcrypto example in docs - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #8467: Slightly confusing pgcrypto example in docs
Date
Msg-id 20140213203920.GE32126@momjian.us
Whole thread Raw
In response to Re: BUG #8467: Slightly confusing pgcrypto example in docs  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #8467: Slightly confusing pgcrypto example in docs
List 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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

Attachment

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: Need Information
Next
From: Tom Lane
Date:
Subject: Re: BUG #9210: PostgreSQL string store bug? not enforce check with correct characterSET/encoding