Yes, i am able to reproduce the problem in Linux but not in windows. I am attaching the fix for this issue. After applying this fix, the behaviour in windows and linux are same.
Kindly let me know if i miss anything here.
Still not quite right I'm afraid. If I open a user account with no pre-existing expiry, then the dialogue will try to execute:
ALTER ROLE rolename
VALID UNTIL 'infinity';
As I haven't changed anything on the dialogue, it shouldn't try to make any changes (or, enable the OK button). Also, the dialogue itself shows the current date - it should be blank. If I choose a date - then it still tries to set the expiry to infinity!
Tested on Mac.
Thanks for your inputs. In the current implementation, if the "calender control" doesn't have a proper value, then we do add "infinity" to the sql statement. It's the same case, in the edit/creating a role.
I am not sure, whether we need to follow this implementation or not. I mean, adding "infinity" to the end of sql statement if the calender control value is an empty.
But, i have removed this "infinity" condition and attaching the patch.
Yes, i am able to reproduce the problem in Linux but not in windows. I am attaching the fix for this issue. After applying this fix, the behaviour in windows and linux are same.
Kindly let me know if i miss anything here.
Still not quite right I'm afraid. If I open a user account with no pre-existing expiry, then the dialogue will try to execute:
ALTER ROLE rolename
VALID UNTIL 'infinity';
As I haven't changed anything on the dialogue, it shouldn't try to make any changes (or, enable the OK button). Also, the dialogue itself shows the current date - it should be blank. If I choose a date - then it still tries to set the expiry to infinity!