Forcing a unique login per user row, making sure code can handle it #176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
The DB table
ezuser
allows non-unique values in thelogin
column. That obviously does not make any sense. This pull request is changing the DB schema forcing unique values in thelogin
column. It also adjusts the kernel code which is required to avoid fatal errors creating users in the admin backend.Testing Instructions
php update/run.php -u ezpub -p ezpub -d ezpub