json_to_record Example

2018-05-08 Thread PG Doc comments form
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/functions-json.html
Description:

Hi team,

I had the following issue when going through your
https://www.postgresql.org/docs/current/static/functions-json.html docs.

Looking at the json_to_record example it took me quite a while that it is
not possible to put the json_to_record function right after the the from
clause but instead I would need to put the tables name in front, then use
the json_to_record function. Then put the column definitions behind it and
in the SELECT clause I need to query the columns using the alias. As you use
a * in your examples, I assumed that json_to_record returns all values found
in the json argument of that function.

As an idea I would suggest to provide a sample json which contains key-value
pairs as well as arrays and use this for the whole examples as someone would
rather not query a json written by hand. 

Thank you very much and keep up the good work! I hope you understand and
like my suggestion!

Best regards,

Yoshi


Re: authentication methods sections

2018-05-08 Thread Michael Paquier
On Sat, Apr 21, 2018 at 10:21:03AM -0400, Peter Eisentraut wrote:
> On 4/14/18 17:20, Magnus Hagander wrote:
> > On Thu, Apr 12, 2018 at 2:37 AM, Peter Eisentraut
> >  > > wrote:
> > 
> > I find that the section authentication methods
> >  > > is
> > becoming harder to read and navigate, because we keep adding
> > authentication methods and more information about them, and it's all on
> > one HTML page.  I propose to move those sections up one level in the
> > hierarchy so they end up on separate HTML pages.
> > 
> > 
> > +1, that definitely seems like a good idea. 
> 
> pushed

Sorry for coming late here, but the patch which has been committed,
56811e57, results in a section which is completely empty:
https://www.postgresql.org/docs/devel/static/auth-methods.html

And all the authentication methods get listed here:
https://www.postgresql.org/docs/devel/static/client-authentication.html

So I find the result even more confusing than the original.  Wouldn't it
be more simple to just remove "Authentication Methods" if the current
layer is kept?
--
Michael


signature.asc
Description: PGP signature