Re: Patch author name on commitfest page - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Patch author name on commitfest page
Date
Msg-id AANLkTikhk8bo6QhCycDBxP20tTx1eh8YLooGWJ_6DCM=@mail.gmail.com
Whole thread Raw
In response to Re: Patch author name on commitfest page  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Patch author name on commitfest page
List pgsql-hackers
On Thu, Sep 30, 2010 at 23:45, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Sep 30, 2010 at 5:38 PM, Gurjeet Singh <singh.gurjeet@gmail.com> wrote:
>> Can we please change the comment lines below the patch heading to have the
>> real name instead of the postgresql.org ID?
>>
>> Patch by Pavel Stehule
>> Patch by Gurjeet Singh
>>
>> instead of
>>
>> Patch by okbobcz
>> Patch by singh.gurjeet
>>
>> https://commitfest.postgresql.org/action/commitfest_view?id=8
>
> I don't think that information is available to the app, at least at
> present... when you log in, it is empowered to ask the community login
> DB "is this combination of a username and a password valid?" but all
> it gets back is "yes" or "no".

Sure it is. When you call community_login(), it'll return you the
yes/no field, the full name, the email address, an author text (not
used anymore, so don't rely on that), community docs superuser flag
(also not used, don't rely on, kind of a failed experiment) and last
successful login time prior to this one.

It's quite possible all users haven't included their full name when
they registered, but for those that have the information is available.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: O_DSYNC broken on MacOS X?
Next
From: Magnus Hagander
Date:
Subject: Re: Using streaming replication as log archiving