Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDO/DB Store"
< CDO
(→Features) |
|||
| Line 4: | Line 4: | ||
* Supports all optional features of the [[#CDO_Server|CDO Server]]. | * Supports all optional features of the [[#CDO_Server|CDO Server]]. | ||
| − | * Pluggable SQL dialect adapters. Includes support for [[Derby]], [[H2]], [[HSQLDB]], [[MySQL]], [[PostgreSQL]] and [[Oracle]] . | + | * Pluggable SQL dialect adapters. Includes support for [[Net4j/DB/Derby]], [[Net4j/DB/H2]], [[Net4j/DB/HSQLDB]], [[Net4j/DB/MySQL]], [[Net4j/DB/PostgreSQL]] and [[Net4j/DB/Oracle]] . |
* Pluggable mapping strategies. Includes horizontal mapping strategy (one table per concrete class, no joins). | * Pluggable mapping strategies. Includes horizontal mapping strategy (one table per concrete class, no joins). | ||
* Various mapping options by using EAnnotations on model elements: [http://git.eclipse.org/c/cdo/cdo.git/tree/plugins/org.eclipse.emf.cdo.server.db/src/org/eclipse/emf/cdo/server/internal/db/DBAnnotation.java DBAnnotation.java] | * Various mapping options by using EAnnotations on model elements: [http://git.eclipse.org/c/cdo/cdo.git/tree/plugins/org.eclipse.emf.cdo.server.db/src/org/eclipse/emf/cdo/server/internal/db/DBAnnotation.java DBAnnotation.java] | ||
| − | |||
== Configuration == | == Configuration == | ||
Revision as of 01:38, 18 November 2012
The CDO DB store is an implementation of the CDO IStore that allows to store models and meta models in relational databases. It does not use 3rd party components other than database vendor-specific JDBC drivers. The DB store is a proprietary O/R mapper.
Features
- Supports all optional features of the CDO Server.
- Pluggable SQL dialect adapters. Includes support for Net4j/DB/Derby, Net4j/DB/H2, Net4j/DB/HSQLDB, Net4j/DB/MySQL, Net4j/DB/PostgreSQL and Net4j/DB/Oracle .
- Pluggable mapping strategies. Includes horizontal mapping strategy (one table per concrete class, no joins).
- Various mapping options by using EAnnotations on model elements: DBAnnotation.java
Configuration
- Configuring the DBStore: see CDO/Server_Configuration_Reference#Element_store.