Search

Won’t symphony 2.1 store its datasources and other configurations as flat xml files, and only pure content in the mysql database?… Would it then be possible to have symphony working out of the box with different types of databases?

The SymQL extension might be rewritten for different kinds of databases …. but then all extensions should make use of it…

Possible Databases;

  • flat file (so only requirement is apache + php)
  • SQLite database (like apache and php available out of the box on macosx)
  • mysql (needs install, but likely also the DB of choice for deployment)

I like that when you install django it has a lightweight test-DB (not for production) out of the box so you can start prototyping right away. The question is wether the above DB-options also can/need to be easily converted into mysql for deployment…

Not viable for 2.1, but definitely something that’s been on our minds…

Not to mention XML dbs and SPARQL endpoints, etc.

Document-oriented databases?

I like the concept of document oriented databases and the perceived flexibility they say they offer.

Nice to see how we all love to muse…
BTW: Doesn’t 2.1 need a rewrite of all extensions? In that case, couldn’t they also be rewritten to use SymQL (while we are at it) so they are modular and prepared for future DB independant Symphony versions?

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details