-
Notifications
You must be signed in to change notification settings - Fork 494
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
IQSS/10117-increase-guestbook-question-length #10118
IQSS/10117-increase-guestbook-question-length #10118
Conversation
2023/12/18: Also closes #9492 |
…stion_limit_and_failure
…stion_limit_and_failure
…stion_limit_and_failure
…stion_limit_and_failure
…stion_limit_and_failure
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.
This file needs to be renamed V6.5....
…stion_limit_and_failure
@stevenwinship @qqmyers @ofahimIQSS Jenkins tests are failing. Does anyone know why? |
[Pipeline] script GitHub has been notified of this commit’s build result Finished: FAILURE |
"System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)." |
…stion_limit_and_failure
No issues found during testing - Merging PR |
What this PR does / why we need it: This PR increases the allowed length of a custom question (was 255 chars, now up to limit of the postgres text type) and fixes the code that was hiding any error when a guestbook create/edit failed (due to this or other reason causing a CommandException).
Which issue(s) this PR closes:
Special notes for your reviewer: Accidentally committed to develop, reverted everything, and added a new commit here to restore everything.
Suggestions on how to test this: Try creating/editing a guestbook with a custom question over 255 chars in length. Before the PR, you'll see a success message and no new guestbook/guestbook update. After the PR, the change will succeed. If you also want to test the error fix, run
ALTER TABLE customquestion ALTER COLUMN questionstring TYPE varchar(10);
or similar low number and try to add a question longer than that. (setting TYPE back to text as in the flyway script will restore your db).Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?: fairly minor issue but I added one
Additional documentation: