Wrong sql length measurement in Upgrade Script
Components
Labels
None
Description
Context Information
None
Additional information (do not use)
None
Attachments
1
- 20 May 2011, 10:46 AM
Activity
Show:
Alex September 19, 2011 at 9:08 PM
Closing, since 5.1.3 release has been released.
Alex June 28, 2011 at 1:59 PM
Fix committed to [b]5.1.x branch/b. Commit Message:
Fixes #0001053: Wrong sql length measurement in Upgrade Script
Dmitry Andrejev June 27, 2011 at 1:23 PM
Moving this task to 5.1.3 since kind of important.
Dmitry Andrejev May 23, 2011 at 1:06 PM
Tested good, please move to 5.1.3 and commit.
Fixed
Priority
Assignee
Reporter
Alex
AlexDeveloper
Alex
AlexChange Log Message
Fixes string length measurement in Upgrade Script
Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
External issue ID
1053
External issue URL
Fix versions
Affects versions
Created May 20, 2011 at 10:43 AM
Updated December 29, 2024 at 9:13 PM
Resolved September 19, 2011 at 9:08 PM
During In-Portal upgrade process file "<module-name>/install/upgrades.sql" is processed to match database queries (sql) to one or another In-Portal version. Then sqls from versions, that needs to be executed are executed.
Usually all data in that file is in English, however if someone will place Unicode symbol in there (e.g. character in Russian), then whole sql-version-match stuff will fail.