Changes for page How To create and update Databases using SchemaManager and SchemaUpdateSnippets

Last modified by christoph_lechleitner@iteg_at on 2013-01-31 07.32:56

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Children
- Content
- Comments
- Attachments
- History
- Information

From 2.1 to 1.1 From 5.1 to 4.1

From version 4.1

edited by christoph_lechleitner@iteg_at
on 2013-01-31 04.25:51

Change comment: Name of schema history table configurable now, and text refactoring

To version 2.1

edited by 5fbc055b7cc103006957e1ae
on 2012-06-14 06.29:38

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.christoph_lechleitner@iteg_at
++XWiki.5fbc055b7cc103006957e1ae

Content

@@ -1,11 +1,9 @@
  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Preliminary"/}}Preliminary =
--The SchemaManager ({{code language="none"}}org.clazzes.jdbc2xml.schema.SchemaManager{{/code}}) and SchemaEngine provide means to maintain the database scheme of an application, allowing you to add and delete tables, columns, relations and data in the database along application updates.
++The SchemaManager and SchemaEngine give you an abstracted access to the database schema of your application, allowing you to add and delete tables, columns, relations and data in the database on application updates. It uses a designated table to keep track of the current schema status, which it will check whenever it is run, and update the database if it is not at the correct version.
--==== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-SchemaHistoryTable"/}}Schema History Table ====
++SchemaManager ({{code language="none"}}org.clazzes.jdbc2xml.schema.SchemaManager{{/code}}) will create a table called SCHEMA_HISTORY if it can not find it the first time it is run. This table contains the following columns:
--A designated schema table, by default named SCHEMA_HISTORY, is used to keep track of the current scheme. It will be automatically at SchemaManager's first run. (% style="font-size: 10.0pt;line-height: 13.0pt;" %)SCHEMA_HISTORY contains the following columns:
--
  {{code language="none"}}
  VERSION:varchar(10), not null, primary key
  DESCRIPTION:varchar(512), nullable
@@ -13,21 +13,17 @@
  SERIALNR:integer(5), not null
  {{/code}}
--In (% style="font-size: 10.0pt;font-weight: normal;line-height: 13.0pt;" %)heterogenous environments as well as in heavily modularized software architectures a single database may be shared by multiple parties each requiring a couple of tables.
--
--(% style="font-size: 10.0pt;font-weight: normal;line-height: 13.0pt;" %)To allow multiple modules (applications, libraries, other OSGi bundles) to use (% style="font-size: 10.0pt;line-height: 13.0pt;" %)JDBC2XML's SchemaManager concurrently within one database, as of JDBC 1.1.1 SchemaManager hold the name of the schema history table in an overwritable property, {{code language="none"}}versionHistoryTable{{/code}}. See (%%)[[JDBCTOXML-11>>url:https://jira.clazzes.org/browse/JDBCTOXML-11||shape="rect"]](% style="font-size: 10.0pt;line-height: 13.0pt;" %).
--
  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-ProjectConfiguration"/}}Project Configuration =
--SchemaManager requires a DataSource ({{code language="none"}}javax.sql.DataSource{{/code}}) and a list of TableInfo ({{code language="none"}}org.clazzes.jdbc2xml.schema.TableInfo{{/code}}) Objects, from which database structures will be created if an "empty" database is detected. Furthermore, an implementation of ISchemaEngine ({{code language="none"}}org.clazzes.jdbc2xml.schema.ISchemaEngine{{/code}}) is required.
++To function correctly, SchemaManager needs a DataSource ({{code language="none"}}javax.sql.DataSource{{/code}}) and a list of TableInfo ({{code language="none"}}org.clazzes.jdbc2xml.schema.TableInfo{{/code}}) Objects, from which a database will be created if it finds an empty database. To function properly, it also needs an implementation of ISchemaEngine ({{code language="none"}}org.clazzes.jdbc2xml.schema.ISchemaEngine{{/code}}).
--Optionally, a base version (default value 0.1.00) and a base description String (default "initial database schema") may be specified.
++Optionally, you may set the base version (default value 0.1.00) and base description String (default "initial database schema").
  Database updates are passed as a Map<String, ISchemaUpdateSnippet> (org.clazzes.jdbc2xml.schema.ISchemaUpdateSnippet) - details see below.
  To perform the operations, call {{code language="none"}}SchemaManager.start(){{/code}}.
--=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-ConfigurationusingSpringorOSGi/Blueprint"/}}Configuration using Spring or OSGi/Blueprint ===
++=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-UsingSpringorOSGi/Blueprint"/}}Using Spring or OSGi/Blueprint ===
  If you are using OSGi with Blueprint or Spring to set up your project, you can configure a SchemaManager instance by adding the following to your blueprint {{code language="none"}}services.xml{{/code}} (or Spring configuration file):
@@ -39,7 +39,7 @@
  </bp:reference>
  <bp:bean id="sqlDialect" factory-ref="dialectFactory" factory-method="newDialect">
--<bp:argument ref="jdbcUrl"><!-- bean jdbcUrl specified above -->
++<bp:argument> <!-- Pass JDBC URL as an argument -->
  </bp:argument>
  </bp:bean>
@@ -51,32 +51,22 @@
  <bp:bean id="databaseSetup" class="org.clazzes.jdbc2xml.schema.SchemaManager" init-method="start">
  <bp:property name="dataSource" ref="dataSource"></bp:property>
  <bp:property name="schemaEngine" ref="schemaEngine"></bp:property>
--    <!-- optional but recommended: special name for schema history table: -->
--    <bp:property name="versionHistoryTable" value="MYLIB_SCHEMA_HISTORY"/>
--    <!-- optional but recommended: explicit first version -->
  <bp:property name="baseVersion" value="0.1.00" />
  <bp:property name="baseTables">
--<!-- List of TableDefinitions here (see below), typical: -->
--        <!-- <bp:bean factory-ref="tableDefinitions" factory-method="getSetup" /> -->
++<!-- Add List of TableDefinitions here -->
  </bp:property>
  <bp:property name="upateSnippets">
  <!-- Add Update-Snippets here -->
--        <!-- Example for update from 0.1.00 to 0.1.01 -->
--        <!-- <bp:entry key="0.1.00" value="foo.schema.SchemaUpdate_0_1_01"></bp:entry> -->
  </bp:property>
  </bp:bean>
  {{/code}}
--By default, JDBC2XML provides an implementation of IDialectFactory and ISchemaEngineFactory as an OSGi service or via ServiceRegistry for Spring.
++By default, JDBC2XML provides an implementation of IDialectFactory and ISchemaEngineFactory as an OSGi service or via ServiceRegistry lookup for Spring.
  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Settingupaninitialdatabaseschema"/}}Setting up an initial database schema =
--To create an initial database schema, SchemaManager needs a list of TableInfo objects.
++To create an initial database schema, you will need to provide SchemaManager with a list of TableInfo objects. The recommended way to do this is to provide a class in your project which creates this list in it's constructor and provides it through a getter. You can instantiate this class in your Spring/Blueprint config as a singleton, and feed the provided List to SchemaManager. An example of this class could look like this:
--The recommended strategy is to implement a table definition class providing this list through a getter.
--
--This is an example:
--
  {{code language="java"}}
  package org.clazzes.example.jdbc2xml;
@@ -91,7 +91,8 @@
  public class TableDefinitions {
--    // It is adviseable to provide the Strings used as names for tables and columns as constants, so they can be reused outside this object to build sql-statements
++    /* It is adviseable to provide the Strings used as names for tables and columns as
++       constants, so they can be reused to build sql-statements */
      public static final String TB_EXAMPLE_TABLE_NAME = "ADDRESSBOOK";
      public static final String COL_EXAMPLE_ID = "ID";
      public static final String COL_EXAMPLE_NAME = "NAME";
@@ -98,12 +98,12 @@
      public static final String COL_EXAMPLE_ADDRESS_REF = "ADDRESS";
      public static final String COL_EXAMPLE_BIRTHDAY = "BIRTHDAY";
--    // ...
++    /* ... */
      private List<TableInfo> setup;
      public TableDefinitions() {
--// Create a table
++/* Create a table */
  TableInfo exampleTable = new TableInfo(TB_EXAMPLE_TABLE_NAME);
  exampleTable.setColumns(
              Arrays.asList(new ColumnInfo[] {
@@ -113,21 +113,21 @@
  new ColumnInfo(COL_EXAMPLE_BIRTHDAY, Types.DATE, 12, null, false, null)
  }));
--// Example for creating a foreign key reference
++/* Example for creating a foreign key reference */
  exampleTable.setForeignKeys(Arrays.asList(new ForeignKeyInfo[] {
  new ForeignKeyInfo("FK_EXAMPLE_ADDRESS", COL_EXAMPLE_ADDRESS_REF, TB_ADDRESS, COL_ADDRESS_ID)
  }));
--// Example for creating a primary key
++/* Example for creating a primary key */
  exampleTable.setPrimaryKey(
  new PrimaryKeyInfo("PK_EXAMPLE", COL_EXAMPLE_ID)
  );
--// ...
++/* ... */
  this.setup = Arrays.asList(
  exampleTable,
--// ...
++/* ... */
  );
      }
@@ -141,111 +141,20 @@
  You must inject {{code language="none"}}TableDefinitions.getSetup(){{/code}} into {{code language="none"}}SchemaManager.setBaseTables(){{/code}} before calling {{code language="none"}}SchemaManager.start(){{/code}}.
--Using Blueprint/Spring, you can do this by inserting the following snippet in the bean definition for SchemaManager:
++Using Blueprint/Spring, you can do this with the following snippet:
--{{code language="html/xml"}}
--<!-- SchemaManager bean definition starts here ... -->
--<bp:property name="baseTables">
--<bp:bean factory-ref="tableDefinitions" factory-method="getSetup" />
--</bp:property>
--<!-- ... and continues here -->
++{{code language="none"}}
++
  {{/code}}
--= {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-UpdatingadatabaseschemawithISchemaUpdateSnippet"/}}Updating a database schema with ISchemaUpdateSnippet =
++= {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-UpdatingadatabaseschemawithSchemaUpdateSnippets"/}}Updating a database schema with SchemaUpdateSnippets =
  To update the database or it's content with schema updates, you must create a new implementation of ISchemaUpdateSnippet ({{code language="none"}}org.clazzes.jdbc2xml.schema.ISchemaUpdateSnippet{{/code}}) for each consecutive update. SchemaManager takes a {{code language="none"}}Map<String, Class<? extends ISchemaUpdateSnippet>>{{/code}} which contains the update classes keyed by the originating (e.g. previous) version.
--An example for an implementation of a schema update snippet could look like this:
++
--{{code language="java"}}
--package org.clazzes.example.jdbc2xml.updates;
++
--import java.sql.SQLException;
--import java.sql.Types;
--import java.util.Arrays;
--import org.clazzes.jdbc2xml.schema.ColumnInfo;
--import org.clazzes.jdbc2xml.schema.ISchemaEngine;
--import org.clazzes.jdbc2xml.schema.ISchemaUpdateSnippet;
--import org.clazzes.jdbc2xml.schema.PrimaryKeyInfo;
--import org.clazzes.jdbc2xml.schema.TableInfo;
--
--public class SchemaUpdate0_1_01 implements ISchemaUpdateSnippet {
--
--// This is only accessed through the getter
--private static final String TARGET_VERSION = "0.1.01";
--
--// Here it is also adviseable to define constants for reuse in statements.
--public static final String COL_EXAMPLE_GENDER = "GENDER";
--
--
--@Override
--public String getTargetVersion() {
--return TARGET_VERSION;
--}
--
--@Override
--public String getUpdateComment() {
--return "Adding column "+COL_EXAMPLE_GENDER+" to table "+TableDefinitions.TB_EXAMPLE_TABLE_NAME+".";
--}
--
--@Override
--public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
--TableInfo ti = schemaEngine.fetchTableInfo(TableDefinitions.TB_EXAMPLE_TABLE_NAME, null);
--        schemaEngine.addColumn(ti, new ColumnInfo(COL_EXAMPLE_GENDER, Types.VARCHAR, 1, null, true, null));
--}
--}
--
--
--{{/code}}
--
--The return values of {{code language="none"}}ISchemaUpdateSnippet.getTargetVersion(){{/code}} and {{code language="none"}}ISchemaUpdateSnippet.getUpdateComment(){{/code}} are written to the {{code language="none"}}SCHEMA_HISTORY{{/code}} table. The update itself is performed in {{code language="none"}}ISchemaUpdateSnippet.performUpdate(){{/code}}. In the above example, it adds a column called {{code language="none"}}GENDER{{/code}} to the example table created by the TableDefinitions class above.
--
--To add an entire table you would use the {{code language="none"}}ISchemaEngine.createTable(){{/code}} method, like this:
--
--{{code language="java"}}
--@Override
--public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
--        TableInfo tiGroup = new TableInfo(TB_GROUP);
--        tiGroup.setColumns(Arrays.asList(new ColumnInfo[] {
--                new ColumnInfo(TableDefinitions.COL_ID, Types.VARCHAR, 36, null, false, null),
--                new ColumnInfo(TableDefinitions.COL_NAME, Types.VARCHAR, 100, null, false, null),
--                new ColumnInfo(TableDefinitions.COL_DESCRIPTION, Types.VARCHAR, 512, null, true, null)
--        }));
--        tiGroup.setPrimaryKey(new PrimaryKeyInfo(PK_GROUP, TableDefinitions.COL_ID));
--        tiGroup.setIndices(Arrays.asList(new IndexInfo(IDX_GROUP_01, TableDefinitions.COL_NAME, true, null)));
--
--schemaEngine.createTable(tiGroup, true);
--}
--{{/code}}
--
--Executing a PreparedStatement also works, using ISchemaEngine.getConnection() to retrieve the database connection:
--
--{{code language="java"}}
--@Override
--public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
--        String sql = "UPDATE "+TableDefinitions.TB_EXAMPLE_TABLE_NAME+" SET "+TableDefinitions.COL_EXAMPLE_NAME+"=?";
--
--        PreparedStatement ps = schemaEngine.getConnection().prepareStatement(sql);
--
--        ps.setNull(1, Types.VARCHAR);
--
--        ps.execute();
--}
--{{/code}}
--
--To create the map of updates in Blueprint/Spring and inject them into SchemaManager, use the following xml-Snippet:
--
--{{code language="html/xml"}}
--<!-- SchemaManager bean definition starts here ... -->
--<bp:property name="upateSnippets">
--<bp:map>
--<bp:entry key="0.1.00" value="org.clazzes.example.jdbc2xml.updates.SchemaUpdate0_1_01"></bp:entry>
--<!-- more entries come here: "key" is the schema version to update, "value" the qualified classname of the schema update -->
--</bp:map>
--</bp:property>
--<!-- ... and continues here -->
--{{/code}}
--

Confluence.Code.ConfluencePageClass[0]

Id

@@ -1,1 +1,1 @@
--656825
++656809

URL

@@ -1,1 +1,1 @@
--https://clazzes.atlassian.net/wiki/spaces/JDBC2XML/pages/656825/How To create and update Databases using SchemaManager and SchemaUpdateSnippets
++https://clazzes.atlassian.net/wiki/spaces/JDBC2XML/pages/656809/How To create and update Databases using SchemaManager and SchemaUpdateSnippets

Changes for page How To create and update Databases using SchemaManager and SchemaUpdateSnippets

Summary

Details

Applications

Navigation

Need help?