Closed
Bug 701865
Opened 14 years ago
Closed 14 years ago
balrog needs to use LONGTEXT for the Releases' table data column
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(1 file)
|
4.43 KB,
patch
|
nthomas
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Up until now we've been using Text, which translates to MySQL's TEXT. When I tried importing data into the MySQL database, it got truncated. Using MySQL's LONGTEXT fixes that. Unfortunately, there's no generic way to specific this, so we need to special case MySQL in the Releases table.
Attachment #573913 -
Flags: review?(nrthomas)
|
||
Comment 1•14 years ago
|
||
Comment on attachment 573913 [details] [diff] [review]
pass dialect to tables; use LONGTEXT when needed
4GB should be enough for anyone!
Attachment #573913 -
Flags: review?(nrthomas) → review+
|
Assignee | |
Comment 2•14 years ago
|
||
Comment on attachment 573913 [details] [diff] [review]
pass dialect to tables; use LONGTEXT when needed
Jenkins run: https://jenkins.mozilla.org/job/Balrog/34/
Attachment #573913 -
Flags: checked-in+
|
|
Assignee | |
Comment 3•14 years ago
|
||
Used manage-db.py to recreate releases & releases_history in the dev env, worked fine!
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•