For a particular project, I'm not yet committed to either MySQL (and its forks) or PostgreSQL. How difficult would it be to develop a DB model in EA using one DB, then possibly migrating to another. Since EA doesn't seem to allow starting with a Conceptual DB Model--last time I used it, I believe I had to choose a specific DB type to start building a DB model.
One issue I'm facing--I know very little about MySQL other than that it's quite common for use on the web and very fast. But it seems not to be a full-fledged RDBMS, e.g. at some point--possibly even the present--it doesn't or didn't have FK constraints (that would be a show stopper for me because that sort of biz logic I prefer to have the RDBMS enforce).
Whereas PostgreSQL is a full-fledged RDBMS, evidently close in feature parity to SQL Server and Oracle. At least to the extent that, if you follow the GIS vendor Esri (of which EA supports developing ArcGIS geodatabases), PostgreSQL is one of the DB platforms Esri supports for Enterprise geodatabases--but not MySQL.
There are a number of recent threads about the MySQL version. MariaDB is not officially supported, but as it is from the same developer as MySQL (actually the prefixes are the names of his daughters) you can try to replace MySQL with MariaDB. This is just a good guess, not based on any experience.
No idea about DB2 and PostgreSQL. I only know that people had good experiences with the latter according to their posts here. You could mail Sparx sales support for details.
q.