Closed
Bug 1009395
Opened 11 years ago
Closed 11 years ago
Set explicit engine=InnoDB when creating the tables
Categories
(Cloud Services Graveyard :: Server: Sync, defect, P1)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Assigned: rfkelly)
Details
(Whiteboard: [qa+])
Attachments
(1 file)
|
701 bytes,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
When used with older versions of MySQL, the current storage script will create tables using the default MyISAM engine. That's bad, since it doesn't support transactions and we use transactions. So we should explicitly declare engine=InnoDB.
(This is related to, but not the same as, Bug 1009389 which is affected by ops deployment scripts rather than the app's own table-created routines)
|
Assignee | |
Comment 1•11 years ago
|
||
Assignee: nobody → rfkelly
Attachment #8421521 -
Flags: review?(telliott)
|
||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Whiteboard: [qa+]
|
|
||
Updated•11 years ago
|
Attachment #8421521 -
Flags: review?(telliott) → review+
|
|
Assignee | |
Comment 2•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
|
||
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•