Repository navigation
[rc-1.6.0] Schema: widen the user name columns on servers upgraded from 1.5 - #2006
Merged
Merged
Conversation
Step 279 widens users.uName and users.uCreateBy from 1.5's VARCHAR(40) NOT NULL to VARCHAR(255) NULL. A 1.5.x server arrives with a count past 279 and skips it, and SchemaReconciler never retypes an existing column. So an upgraded server kept a 40-character user name, where a fresh install allows 255. Step 446 repeats the ALTER. Widening keeps every stored value, and on a server that already ran 279 it changes nothing. Refs #2000 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Port of #2005 to
rc-1.6.0. The cherry-pick applied cleanly, andtests/schema-gate.test.phppasses on this branch.Refs #2000
🤖 Generated with Claude Code