In version 6.4.1 we have the following SQL "CREATE UNIQUE INDEX ezuser_login ON ezuser USING btree ((lower(login)));
" in current/vendor/ezsystems/ezpublish-kernel/data/update/postgres/dbupdate-6.3.0-to-6.4.0.sql. Doesn't this mean that we can't have duplicate values within the login field? But if I create a user within the admin (Legacy admin), leave that draft as untouched. Then attempt to create another I will effectively have 2 records in the DB with a login of "" which will throw a SQL error. Is there a proposed solution for this? At the moment we have had to remove this unique key.

EZP-19614 is also the proposal of adding the unique key, even in this task the issues are identified.

Any help or advice would be appreciated.

Thanks,
Joe Jones