Comment 6 for bug 1480678

As reported by Maxim Baele, the version 1.22.0 from 16.04 does crash when trying to edit the properties of a role that does not have the expiration date set. I just confirmed it by setting the expiration date of one of the roles while keeping the others unset. All but the one with the expiration set crashes pgadmin3.

Given that, it is possible to workaround this by setting an expiration date to all users using psql and a command like:

   alter role postgres with valid until '9999-12-31';

I know that this is not the same as a role without expiration date set but it is working in practice.

I think that this new bug may be related to the fix of an annoying bug present on the pgadmin3 from 14.04 that always set the expiration date of users with no expiration to today.