Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Medium Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Joe Jones
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: