Database compliancy

It is one of the important goals of MetaModel to be compliant with as many databases and datastores as possible! We ensure a broad compliance by several initiatives:

  • A broad integration test suite.
  • Extensive but fault-tolerant use of the Java DataBase Connectivity (JDBC) specification.
  • Use of uniform SQL-99 compliant queries.

Relational databases known to be working with MetaModel

DatabaseVersionJDBC driverCompliancy
MySQL5+Connector/JFully compliant
PostgreSQL8+PostgreSQL JDBC driverFully compliant
Oracle10gSQLJ/JDBCFully compliant
Apache Derby10+Derby driverFully compliant
Firebird SQL2.0+Jaybird driverFully compliant
Hsqldb/HyperSQL1.8+Hsqldb driverFully compliant
H21.2+H2 driverFully compliant
SQLite3.6.0+Xerial driverFully compliant
Microsoft SQL Server2005 (+ possibly others)JTDS driverFully compliant
Ingres-Ingres JDBC driverFully compliant

Non-relational / NoSQL databases supported by MetaModel

DatabaseCompliancy
MongoDBFully compliant

File formats supported by MetaModel

File formatFile extensionVersionCompliancy
Comma separated file.csv-Fully compliant
Microsoft Excel spreadsheet.xlsExcel '97-2003Fully compliant
.xlsxExcel 2007+Fully compliant
OpenOffice.org database.odbOpenOffice 2.0+Fully compliant
XML file (SAX based).xml-Fully compliant
XML file (DOM based).xml-Experimental
Microsoft Access database.mdbAccess '97-2003Fully compliant
.accdbAccess 2007+Fully compliant
dBase database.dbf-Fully compliant

Composite datastores

MetaModel supports an advanced feature called composite datastores. In short it means that it's possible to access and query several datastores as if they where one. This involves transparent client-side joining, filtering, grouping etc. Composite datastores are typically not as performant in terms of querying but provides for a convenient way to combine data that is otherwise inherently separated from each other.