文件名称：Making_the_EcoSpace_persistent
文件大小：169KB
文件格式：PDF
更新时间：2011-08-10 12:49:34
eco
Until persistence is added all changes to objects in the EcoSpace will be lost when the application terminates. Prolonging the
life of these objects beyond the life of the application is a very simple process. By adding an ECO persistence component to
the EcoSpace it is possible to update a persistence storage with changes made during the application's execution, this
persistence storage might be a local XML file, a number of supported database servers, or a custom persistence mechanism
to work with persistence storages that are not supported by default.
Summary
Making an EcoSpace persistent is a very simple process. As a consequence switching to a new database can be achieved
in seconds. It is also possible with a small amount of programming to identify which type of database server to connect to at
runtime, allowing your application to connect to the database of your customer's choice.
Database structure management
ECO is not only capable of creating your database structure, but also updating the database structure to reflect changes
made to your business model. Automatic database structure management saves the developer a considerable amount of
time when creating applications.
Supported databases
At the time of writing the following databases are supported by ECO.
• BlackFish.
• DB2 (via Delphi BDP or DBX components).
• InterBase (via Delphi BDP or DBX components).
• FireBird 2.
• MySQL.
• Oracle.
• SQL Server.
• Sybase (via Delphi BDP or DBX components).
• XML file.
More advanced persistence techniques such as mapping to an existing database, reverse engineering an existing database,
and using a remote persistence server will be covered in a subsequent document.