I've tested it on the project on which I had the issue described in ML, the MySQL db now works normally without the need of having HAS_HSTORE set on its settings.
Coverage remained the same when pulling fef72cb5354651fe87dc9280a362da3428efa61f on vendor-check into 9d43341defcc5859f4d24344bed0f1d355315860 on master.
fixes #26
I've tested it on the project on which I had the issue described in ML, the MySQL db now works normally without the need of having HAS_HSTORE set on its settings.