Wikiadmin: Halaman baru: DBSourceManager dari Etendo Documentation, rebrand Etendo→InfiniteERP. Database independence via DDLUtils, Oracle/PostgreSQL support, export.database/update.database/export.config.script tasks, Model filters.

2026-09-21T02:04:46Z

Halaman baru: DBSourceManager dari Etendo Documentation, rebrand Etendo→InfiniteERP. Database independence via DDLUtils, Oracle/PostgreSQL support, export.database/update.database/export.config.script tasks, Model filters.

New page

{{Languages}}
{{BackTo|Main Page}}

= DBSourceManager =

'''DBSourceManager''' is a Java library that helps with database tasks related to development. Its most important feature is '''database independence''' — you can focus on the development of database features and let DBSourceManager deal with the database implementation details.

DBSourceManager is based on [https://db.apache.org/ddlutils/ DDLUtils] and the database model used by DBSourceManager is an extension of the model used by DDLUtils. DDLUtils supports a large list of database engines, but all the extensions created in DBSourceManager only work for '''Oracle''' and '''PostgreSQL'''.

The main goal of DBSourceManager is to aid the developer in the creation and maintenance of database physical objects and data. The way this works is via an array of <code>XML</code> files which represent database physical objects or table records. DBSourceManager contains utilities which allow the developer to export its objects into these <code>XML</code> files, and which allow modifications in these <code>XML</code> files to be moved into the database by updating it.

Therefore, the developer can focus on creating and changing its components (either in the database or in the <code>XML</code> files), and DBSourceManager can automatically move the changes in either place to the other.

== Architecture ==

As previously stated, DBSourceManager is based on the DDLUtils Apache project. Internally, its structure can be described as:

* A series of classes to handle the '''Database model'''
* A series of classes which are related to how the objects and their changes are transformed into '''RDBMS-specific commands'''

== Common Tasks ==

The main tasks which DBSourceManager allows the developer to do are the following:

=== export.database ===

This task generates <code>XML</code> files corresponding with the database physical objects and the Application Dictionary table contents. It exports everything from the database so that the XML files reflect the current state of the database.

See [[Development Build Tasks#export.database|export.database]] in Development Build Tasks for usage details.

=== update.database ===

This task updates the database, applying the changes which are necessary to transform it so that it follows the model described in the <code>XML</code> files. It reads the XML files and applies any differences to the database.

See [[Development Build Tasks#update.database|update.database]] in Development Build Tasks for usage details.

=== export.config.script ===

This task generates a configuration script of the current system.

== Model Filters ==

DBSourceManager uses a mechanism which is called '''Model filters''' to purposely remove some unwanted objects from the physical database model. These filters can be extended by modules.

To know how to exclude database physical objects from the model, see [[How to exclude Database Physical Objects From Model]].

== Relationship with Build Tasks ==

DBSourceManager tasks are integrated into the InfiniteERP build system. The main tasks are executed as Ant tasks:

* <code>ant export.database</code> — exports the current database state to XML files
* <code>ant update.database</code> — updates the database from XML files
* <code>ant export.config.script</code> — exports the configuration script

These tasks are related to [[Modularity Concepts|modularity concepts]] in InfiniteERP. When developing modules, only modules "in development" are exported by DBSourceManager.

== Relationship with InfiniteERP Architecture ==

DBSourceManager plays a key role in the InfiniteERP development workflow:

* It enables '''database independence''' — the same XML files can be used for both Oracle and PostgreSQL
* It supports the '''Model Driven Development''' approach by keeping database schema in sync with the Application Dictionary
* It enables modular development by allowing modules to export their own database changes independently
* It works together with [[Data Access Layer]] to keep the runtime model and the database in sync

== See Also ==

* [[Development Build Tasks]] — for details on Ant tasks including export.database and update.database
* [[Data Access Layer]] — for how DBSourceManager interacts with the DAL
* [[Modularity Concepts]] — for how DBSourceManager supports modular development
* [[How to exclude Database Physical Objects From Model]] — for Model filters
* [[Application Dictionary]] — for the metadata that DBSourceManager manages

== References ==

* [https://docs.etendo.software/developer-guide/etendo-classic/concepts/dbsourcemanager/ DBSourceManager — Etendo Documentation]

----

''This work is a derivative of [http://wiki.openbravo.com/wiki/DBSourceManager DBSourceManager] by [http://wiki.openbravo.com/wiki/Welcome_to_Openbravo Openbravo Wiki], used under [https://creativecommons.org/licenses/by-sa/2.5/es/ CC BY-SA 2.5 ES]. This work is licensed under [https://creativecommons.org/licenses/by-sa/2.5/ CC BY-SA 2.5].''

[[Category:Developers Guide]]
[[Category:Documentation ERP]]
[[Category:Concepts]]

DBSourceManager - Revision history

Wikiadmin: Halaman baru: DBSourceManager dari Etendo Documentation, rebrand Etendo→InfiniteERP. Database independence via DDLUtils, Oracle/PostgreSQL support, export.database/update.database/export.config.script tasks, Model filters.