Open kcrwfrd opened 12 years ago
It is still the case due to the way the CMS works with schemaless databases. You could use a different type of schemaless database, but not MySQL. In order to use MySQL, you would need to ensure schema changes were made when new plugins to the CMS were created that manipulated the core models.
This is what Drupal does for example. While it could probably be done more elegantly with the filter system, it's still something that's not inside the scope of this CMS nor on the roadmap.
Schema changes like this back and forth create a problem with maintenance for a system and a relational database in general like MySQL is simply a poor choice for a CMS. While the MySQL database is popular, it's simply the wrong database for something like this. It is also ultimately the one of the main reasons for the failure of systems like Drupal, WordPress, etc. with regard to handling traffic load and general maintenance from a developer's perspective.
Thanks for the info. Makes sense.
I was very excited about this project, but then I read on http://www.shift8creative.com/blog/getting-started-with-minerva that it will only support MongoDB and not MySQL, and it was a huge let down :(
Is this still the case? What about in the future?