Modify ↓
Opened 9 years ago
Last modified 14 months ago
#12097 new enhancement
Add a script to contrib for converting MySQL storage engine
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | database backend | Version: | |
| Severity: | normal | Keywords: | mysql |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
User in SO:29982115/121694 claims to get an error The current storage engine is MyISAM. It must be InnoDB or NDB storage engine to support transactions after upgrading to Trac 1.0.2. That is what I'd expect after #10993.
I see that we've documented a fix in MySqlDb#Conversion. Would it be feasible to provide a script in contrib for fixing the storage engine and collation? That might help less experienced users.
I'm requesting feedback on whether this is a good idea before trying to create a script.
Attachments (1)
Change History (4)
by , 9 years ago
| Attachment: | innodb.sql added |
|---|
comment:1 by , 8 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:2 by , 5 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x |
|---|
Note:
See TracTickets
for help on using tickets.
Native MySQL script to change MyISAM tables to InnoDB tables.