Great Job on fixing the issue/problem!
When I google this search term: “BLOB/TEXT column cant have a default value for query CREATE TABLE” I see that this is a known issue/problem with MySQL versions 5 to 5.5 and maybe higher versions.
http://stackoverflow.com/questions/3466872/why-cant-a-text-column-have-a-default-value-in-mysql
http://bugs.mysql.com/bug.php?id=21532
MariaDB is modeled after MySQL and has the same Core structure as MySQL and most of the same functionality as MySQL. Since you are the first person to report this issue/problem then this is obviously an isolated issue/problem. We will look into this further, but since this is the first time anyone has reported this issue/problem then I think it is smarter to handle this like an isolated issue/problem instead of changing things that work in all other cases.
We will install and test LudicrousDB, but this is going to be a low priority thing so it will take some time to get around to testing this plugin. The DB Monitor feature is pending additional work to be considered fully completed. Currently DB monitoring of specific tables is actually more of a nuisance than a benefit. The DB Monitor check for new tables created is beneficial, but the check for actual changes made to specific tables is too general. DB Monitor has been put on the back burner for a while and we will get back to focusing on developing that feature further. For now I recommend just using the check for new tables created and not using the Update Time and Table Size advanced checking.
I checked the BPS Pro Development Task Schedule and DB Monitor is going to be worked on in BPS Pro 11.9. Looks like adding an additional option to monitor additional/other databases is going to be added. The primary task is to get DB Monitor to list the exact table|column|row where the change was made and other details about the DB Query and Data.