-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increased the size of the password request table id #10
base: master
Are you sure you want to change the base?
Conversation
Previous the system stopped being able to reset passwords after 255 because of the size of the column
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should also add an upgrade/downgrade script?
How do you suggest this could be done:
|
In the current codebase, I'd go for the first option... |
I've added migrations (option 2) because it was pretty straightforward to do. Sys admins can upgrade their database by following the instructions at the bottom of install.txt Developers can add new migrations by following the docs for Phinx. |
On reflection - I think any change like adding a deployment tool needs to be done in it's own issue, and then the password reset issue can be fixed after that one is there, rather than sneaking it in. I suggest we leave this here, and then return to it once I've had a go at adding a 'proper' update mechanism |
@rcraggs I'm just reviewing some PRs as releasing a new version of WebPA. The DB backend has completely changed since this PR was submitted. We are now making heavy use of Doctrine so I think it might be worth using Doctrine migrations to facilitate this change. For this reason, I think this PR should be closed. Hope that is ok but let me know if you have any reservations. |
Previous the system stopped being able to reset passwords after 255 because of the size of the column. There's no need for the id to be that small.