Can I switch to MariaDB with vb3.8?
 

Is vbulletin 3.8 compatible with MariaDB 10?
Will I run into any problems if I switch from MySQL 5.5 to MariaDB 10?

I'm using MariaDB on my vBulletin 4 installation and it works perfectly fine. MariaDB is basically just a MySQL fork. The functionality is exactly the same as MariaDB, you just keep using the same MySQL extension.

I am currently using mysql 5.5. So this means I should use mysql 5.5 + mariaDB 10? Or is there a minimum version for mariadb?

The difference between MariaDB 10 and 5.5 is that MariaDB 10 has new unique features and contains features ported over from MySQL 5.6. I don't think it matters if you use MariaDB 10 or 5.5, I would just use 5.5 though.

If vbulletin 3.8 is compatible with mysql 5.6 then I will just use mariadb 10.
But I have no clue if vb 3.8 is compatible with mysql 5.6
Does anyone know?

According to vBulletin.com:
You can always give it a shot, it shouldn't be too hard to downgrade in case it does not work.

You have a point there. I asked vb staff some time ago but they did not respond.

I'm running the latest MariaDB 5.5 on vB 3.8 without any issues.

Do you use 3.8.8 or 3.8.7?

As far as I remember, there are no query differences between 3.8.7 & 3.8.8.

(but its over a year since i did most of the changes, so I may have forgotton something).

IIRC this was changed: http://www.vbulletin.com/forum/forum...-dbalter-class
But I altered that anyway and am using mysql 5.5
I wonder if there was anythign more.

You're right, that was fixed in 388, but those are not used in day to day running of the forum anyway.

I see no reason 387/388 would not run happily on mariadb or mysql 5.6.

My local dev server runs mysql 5.6.14, and I have test vb3 sites that run just fine (even my test vb.org, which is vb 3.6.12).

Thanks. This is all very helpful. I'll upgrade to mysql 5.6 first. If that runs well (which seems likely) then I'll go for MariaDB 10 or even Percona if that turns out to be better.

Did both with no problems, now running 3.8.8.

You might be thinking of the PHP version, which can definitely play into this.

im getting loads of this now:

Database error in vBulletin 3.8.7:

Invalid SQL:

INSERT INTO vb_postlog
(postid, useragent, ip, dateline)
VALUES
(1484838, 'Mozilla/5.0 (BlackBerry; U; BlackBerry 9360; en) AppleWebKit/534.11+ (KHTML, like Gecko) Version/7.1.0.258 Mobile Safari/534.11+', 2927070735, 1403684239);

MySQL Error : Data too long for column 'useragent' at row 1
Error Number : 1406

I have set the string to 255 which is the max, but it still results in errors. Probably because of UFT-8. What to do?

Is it a varchar? Max value of a varchar can be 65535, but maybe you should use `text` instead.

Edit: refer to http://stackoverflow.com/a/18459732/1961685 if you want to make the values to be truncated instead of showing the error.

How to convert my current vbulletin database to MariaDB? Should all the tables be converted or just some.

Do the whole database

https://mariadb.com/kb/en/mariadb/do...ql-to-mariadb/

You don't have to change anything in the database yourself, all you're changing is the software. Everything else will be the same.

but do the tables need to be changed to aria engine to utilize MariaDB?

Not sure about vB 3.*, but on vB 4.* I only changed the software and didn't alter the tables or database at all.

my host currently has MariaDB installed, And i did alter some of the Tables to the engine aria and it did made a huge improvement. So i was thinking about doing all the tables.
If you look at this

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +ARCHIVE +Aria +BLACKHOLE +CSV +FEDERATED +InnoDB +MRG_MYISAM
[--] Data in Aria tables: 8M (Tables: 24)
[--] Data in MyISAM tables: 303M (Tables: 379)
[--] Data in InnoDB tables: 1M (Tables: 78)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[--] Data in MEMORY tables: 1020K (Tables: 2)

you will see how much tables are in aria, myisam and innodb, what i was thinking about since my transition from phpbb to vbulletin some of my tables was automatically converted from myisam =to innodb.
So i was thinking the situation will apply here as well to convert the tables to aria to utilize MariaDB.
So i don't know if i'm wrong but i did notice a huge increase in speed when doing so.

"MariaDB uses by default the Aria storage engine for internal temporary files, instead of MyISAM. If you have a lot of temporary files, you should add and set aria-pagecache-buffer-size to the same value as you have for key-buffer-size. "
https://mariadb.com/kb/en/mariadb/do...mysql_upgrade/

Why would you want to switch Databases if they both have just about the same features? MySQL has just been around for a lot longer (I think so anyway), so its a lot older and more mature.

Oh dear... MariaDB is superior for many reasons; MySQL is dying (kind of).

MariaDB is a fork of MySQL thus has everything that MySQL has plus more plus decent support and bug fixes.

See this for all the good reasons to switch:
https://vborg.vbsupport.ru/showthread.php?t=317249

Oh wow, really? I didn't know that. I will have to look into it, maybe I will switch also. Thanks for the info!