The eobjects.org MetaModel is a project created for maximum reuse of a SQL-compliant domain model of the database domain. The MetaModel is a model that contains classes that represent the structure of a database (schemas, tables, column, relationships) and interaction with the database (queries) in a SQL/LINQ-like way. In short, it is a model for modelling data in databases and other datastores. With MetaModel you can query different datastores like databases, CSV files, Excel spreadsheets, MS Access files, and XML files using the same approach and the same domain model.
|Tags||Text Processing Markup XML Software Development Libraries Java Libraries Application Frameworks Database Database Engines/Servers Information Management Records Management Metadata/Semantic Models API|
For the past months we've been working on a proposal to donate the MetaModel project to the Apache Foundation, where it will live initially as an...
Release Notes: This release adds a module for querying and updating Salesforce.com installations, backed by the Salesforce.com Web services. It adds a module for querying SugarCRM installations, backed by SugarCRM Web services. It optimizes support for DB2 queries with firstRow and maxRows properties set, yielding a ROW_NUMBER query in the background database interaction.
Release Notes: Many query parser improvements, including parsing column names with dots, mixed case clause declarations, select DISTINCT queries, select item aliases, and selecting everything from multiple from items. It also fixes two bugs: an issue with interpreting CHAR types as strings, and inclusion of function names (if available) in TableModel header names.
Release Notes: This release fixes timestamp literals on DB2's SQL-dialect.
Release Notes: This release drastically improves the performance of "DELETE FROM" statements on CSV files. It adds mapping of unavailable-to-available data types when issuing "CREATE TABLE" statements containing unavailable data types on e.g. DB2 or PostgreSQL. It fixes a bug pertaining to multi-threaded execution of compiled JDBC queries. A pool of prepared statements has been created to ensure parallel execution of compiled queries. A bug has been fixed pertaining to proper quoting of HAVING clause operands when the data type of the aggregate function is different from the data type of the functions argument.
Release Notes: Queries can now be compiled, preparing them for execution with varying parameter values. For JDBC databases, this will provide prepared statement-like functionality. For other datastores, it will simply make query reuse simpler. DataSet index caching has been implemented, making lookup by column or by "select item" faster and constant-time.