![]() |
|
Thread Tools |
#1
|
|||
|
|||
Converting 'post' & 'thread' Tables to InnoDB - MySQL v5.6
I know that the in the past it was impossible to convert the 'post' and 'thread' tables to InnoDB without losing the full-text capabilities. But now I'm reading that the InnoDB engine in MySQL v5.6+ now supports Full-Text. So is it now possible to convert my tables from MyISAM to InnoDB and still retain full-text capabilities? Will everything still function properly or am I missing something here?
No members have liked this post.
|
#2
|
||||
|
||||
Yes its possible, and in fact we did it on vb.org's database a while ago.
__________________
Former vBulletin.org Staff Member
Cable Forum Please do not PM me about custom work - I no longer undertake any. Note: I will not answer support questions via e-mail or PM - please use the relevant thread or forum. No members have liked this post.
|
#3
|
|||
|
|||
Hey Paul, Thanks for the response.
Once the 'post' and 'thread' tables are converted to InnoDB is it still possible to convert them back to MyISAM later on down the road if things don't work out? Also, right now all my tables are using MyISAM (except of course MEMORY tables) so would it be beneficial for me to only convert just my 'post' and 'thread' tables to InnoDB and leave the rest as MyISAM? Or should I just convert everything to InnoDB? I run a pretty large forum and my post table currently has over 1,003,525 rows. The site runs good but I'm know that table locking on the post and thread tables is definitely killing me. No members have liked this post.
|
#4
|
||||
|
||||
Short answer is yes on converting them back.
You should probably convert your memory tables to INNODB or MyISAM as well. The session table breaks down as a memory table around 50k sessions, not that you're likely to see that on most sites.
__________________
Looking for ImpEx?
No members have liked this post.
|
#5
|
|||
|
|||
Good to know, Thanks for the tip!
What about the other tables? I know that both storage engines have their pros and cons but should I just convert them all to InnoDB or would it be more beneficial to just leave them as MyISAM? No members have liked this post.
|
#6
|
||||
|
||||
Yes. 5.6 is good for the change.
A better alternate is MariaDB (if you can) and Aria tables as this is faster.
__________________
www.AusPhotography.net.au a.k.a. AP is a photography forum where members share their photography, photo editing skills and techniques. We run regular photographic competitions; Rick (site owner) and Kym (site tech) using this account *** Home of the AP fully comprehensive vb4 photographic competition management solution *** No members have liked this post.
|
#7
|
||||
|
||||
Originally Posted by XenonKilla
Unless they are causing you a problem, leave them alone.![]()
Dont make changes for the sake of making changes.
__________________
Former vBulletin.org Staff Member
Cable Forum Please do not PM me about custom work - I no longer undertake any. Note: I will not answer support questions via e-mail or PM - please use the relevant thread or forum. No members have liked this post.
|
#8
|
|||
|
|||
I agree but if something is clearly going to be better then I'd rather do that instead. But yeah MyISAM has been great thus far so I'll probably just leave those other tables alone. Was just fishing for some advice that's all.
![]() No members have liked this post.
|
![]() |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Administrative and Maintenance Tools MyISAM 2 InnoDB - Changes tables engine from MyISAM to InnoDB | PlusVB | vBulletin 3.8 Add-ons | 19 | 20 Jan 2019 15:21 |
«
Previous Thread
|
Next Thread
»
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
|
|
New To Site? | Need Help? |
All times are GMT. The time now is 00:42.