Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires.
От | Akshay Joshi |
---|---|
Тема | Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires. |
Дата | |
Msg-id | CANxoLDeHgFxMRBAg++3mLkGmFjDwJPKqBNz3wkhK99+rq86N8g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires. (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: [pgAdmin][RM-6120]: Adding/updating user should not allow to add an older date in account expires.
|
Список | pgadmin-hackers |
Hi Nikhil
On Thu, Jan 14, 2021 at 2:38 PM Dave Page <dpage@pgadmin.org> wrote:
On Thu, Jan 14, 2021 at 8:18 AM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:Thanks, patch applied.On Thu, Jan 14, 2021 at 11:28 AM Nikhil Mohite <nikhil.mohite@enterprisedb.com> wrote:Hi Team,Please find the attached patch for RM-6120: Adding/updating user should not allow to add an older date in account expires.Added UI validation if a user enters the account expiration date manually.I think this needs to be reverted (and the UI fixed to allow an older date to be selected).
Please fixed as suggested by Dave and send the patch. I'll update the RM
Selecting a past expiry date is a perfectly valid way to create an account that is effectively locked, for example, to allow pre-creation of roles for staff that are yet to join.PostgreSQL doesn't prevent this - why should we?--
Thanks & Regards
Akshay Joshi
pgAdmin Hacker | Principal Software Architect
EDB PostgresMobile: +91 976-788-8246
В списке pgadmin-hackers по дате отправления: