Skip to Content
Last modified by christoph_lechleitner@iteg_at on 2013-01-31 07.32:56
From version 5.1
edited by christoph_lechleitner@iteg_at
on 2013-01-31 06.18:32
Change comment: There is no comment for this version
To version 7.1
edited by christoph_lechleitner@iteg_at
on 2013-01-31 07.32:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,19 +2,64 @@
2 2  
3 3  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.
4 4  
5 -==== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-SchemaHistoryTable"/}}Schema History Table ====
5 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-SchemaHistoryTable"/}}Schema History Table ===
6 6  
7 7  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:
8 8  
9 -{{code language="none"}}
10 -VERSION:varchar(10), not null, primary key
11 -DESCRIPTION:varchar(512), nullable
12 -CREATION_DATE:date, nullable
13 -SERIALNR:integer(5), not null
14 -{{/code}}
9 +|=(((
10 +
11 +)))|=(((
12 +
13 +)))
14 +|(((
15 +(% class="code" %)
16 +(((
17 +VERSION
18 +)))
19 +)))|(((
20 +(% class="code" %)
21 +(((
22 +varchar(10), not null, primary key
23 +)))
24 +)))
25 +|(((
26 +(% class="code" %)
27 +(((
28 +DESCRIPTION
29 +)))
30 +)))|(((
31 +(% class="code" %)
32 +(((
33 +varchar(512), nullable
34 +)))
35 +)))
36 +|(((
37 +(% class="code" %)
38 +(((
39 +CREATION_DATE
40 +)))
41 +)))|(((
42 +(% class="code" %)
43 +(((
44 +date, nullable
45 +)))
46 +)))
47 +|(((
48 +(% class="code" %)
49 +(((
50 +SERIALNR
51 +)))
52 +)))|(((
53 +(% class="code" %)
54 +(((
55 +integer(5), not null
56 +)))
57 +)))
15 15  
16 -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.
59 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-CustomnameforSchemaHistoryTable"/}}Custom name for Schema History Table ===
17 17  
61 +(% style="font-size: 10.0pt;line-height: 13.0pt;" %)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.
62 +
18 18  (% 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;" %).
19 19  
20 20  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-ProjectConfiguration"/}}Project Configuration =
... ... @@ -47,7 +47,10 @@
47 47  <bp:property name="dialect" ref="sqlDialect">
48 48  </bp:property>
49 49  </bp:bean>
95 +
50 50   
97 +<bp:bean id="initialSchema" class="foo.schema.InitialSchema"></bp:bean>
98 + 
51 51  <bp:bean id="databaseSetup" class="org.clazzes.jdbc2xml.schema.SchemaManager" init-method="start">
52 52  <bp:property name="dataSource" ref="dataSource"></bp:property>
53 53  <bp:property name="schemaEngine" ref="schemaEngine"></bp:property>
... ... @@ -57,7 +57,7 @@
57 57  <bp:property name="baseVersion" value="0.1.00" />
58 58  <bp:property name="baseTables">
59 59  <!-- List of TableDefinitions here (see below), typical: -->
60 - <!-- <bp:bean factory-ref="tableDefinitions" factory-method="getSetup" /> -->
108 + <bp:bean factory-ref="initialSchema" factory-method="getSchema" />
61 61  </bp:property>
62 62   <!-- Add Update-Snippets here, example for updates from 0.1.00 to 0.1.01 and on to 0.2.00
63 63  <bp:property name="upateSnippets">
... ... @@ -74,14 +74,16 @@
74 74  
75 75  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Settingupaninitialdatabaseschema"/}}Setting up an initial database schema =
76 76  
125 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-InitalSchema(InitialTableList)"/}}Inital Schema (Initial Table List) ===
126 +
77 77  To create an initial database schema, SchemaManager needs a list of TableInfo objects.
78 78  
79 -The recommended strategy is to implement a table definition class providing this list through a getter.
129 +The recommended strategy is to create an InitialSchema class providing this list through a getter.
80 80  
81 -This is an example:
131 +(% style="font-size: 10.0pt;line-height: 13.0pt;" %)This is an example:
82 82  
83 83  {{code language="java"}}
84 -package org.clazzes.example.jdbc2xml;
134 +package foo.schema;
85 85  
86 86  import java.sql.Types;
87 87  import java.util.Arrays;
... ... @@ -92,40 +92,31 @@
92 92  import org.clazzes.jdbc2xml.schema.PrimaryKeyInfo;
93 93  import org.clazzes.jdbc2xml.schema.TableInfo;
94 94   
95 -public class TableDefinitions {
145 +public class InitialSchema {
96 96  
97 - // 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
98 - public static final String TB_EXAMPLE_TABLE_NAME = "ADDRESSBOOK";
99 - public static final String COL_EXAMPLE_ID = "ID";
100 - public static final String COL_EXAMPLE_NAME = "NAME";
101 - public static final String COL_EXAMPLE_ADDRESS_REF = "ADDRESS";
102 - public static final String COL_EXAMPLE_BIRTHDAY = "BIRTHDAY";
103 - 
104 - // ...
105 - 
106 106   private List<TableInfo> setup;
107 107  
108 - public TableDefinitions() {
149 + public InitialSchema() {
109 109  // Create a table
110 -TableInfo exampleTable = new TableInfo(TB_EXAMPLE_TABLE_NAME);
151 +TableInfo exampleTable = new TableInfo(TableDefs.TABLENAME_ADDRESSBOOK);
111 111  exampleTable.setColumns(
112 112   Arrays.asList(new ColumnInfo[] {
113 -new ColumnInfo(COL_EXAMPLE_ID, Types.BIGINT, 20, null, false, null,true),
114 -new ColumnInfo(COL_EXAMPLE_NAME, Types.VARCHAR, 256, null, false, null),
115 -new ColumnInfo(COL_EXAMPLE_ADDRESS_REF, Types.BIGINT, 20, null, true, null),
116 -new ColumnInfo(COL_EXAMPLE_BIRTHDAY, Types.DATE, 12, null, false, null)
154 +new ColumnInfo(TableDefs.COL_ADDRESSBOOK_ID, Types.BIGINT, 20, null, false, null,true),
155 +new ColumnInfo(TableDefs.COL_ADDRESSBOOK_NAME, Types.VARCHAR, 256, null, false, null),
156 +new ColumnInfo(TableDefs.COL_ADDRESSBOOK_ADDRESS_REF, Types.BIGINT, 20, null, true, null),
157 +new ColumnInfo(TableDefs.COL_ADDRESSBOOK_BIRTHDAY, Types.DATE, 12, null, false, null)
117 117  }));
118 118   
119 -// Example for creating a foreign key reference
120 -exampleTable.setForeignKeys(Arrays.asList(new ForeignKeyInfo[] {
121 -new ForeignKeyInfo("FK_EXAMPLE_ADDRESS", COL_EXAMPLE_ADDRESS_REF, TB_ADDRESS, COL_ADDRESS_ID)
122 -}));
123 - 
124 124  // Example for creating a primary key
125 125  exampleTable.setPrimaryKey(
126 -new PrimaryKeyInfo("PK_EXAMPLE", COL_EXAMPLE_ID)
162 +new PrimaryKeyInfo("PK_EXAMPLE", COL_ADDRESSBOOK_ID)
127 127  );
128 128  
165 +// Example for creating a foreign key reference
166 +exampleTable.setForeignKeys(Arrays.asList(new ForeignKeyInfo[] {
167 +new ForeignKeyInfo("FK_EXAMPLE_ADDRESS", TableDefs.COL_ADDRESSBOOK_ADDRESS_REF, TableDefs.TABLENAME_ADDRESSES, TableDefs.COL_ADDRESS_ID)
168 +}));
169 + 
129 129  // ...
130 130   
131 131  this.setup = Arrays.asList(
... ... @@ -135,23 +135,56 @@
135 135  
136 136   }
137 137    
138 - public List<TableInfo> getSetup() {
139 -return this.setup;
179 + public List<TableInfo> getSchema() {
180 +return this.schema;
140 140   }
141 141  
142 142  }
143 143  {{/code}}
144 144  
145 -You must inject {{code language="none"}}TableDefinitions.getSetup(){{/code}} into {{code language="none"}}SchemaManager.setBaseTables(){{/code}} before calling {{code language="none"}}SchemaManager.start(){{/code}}.
186 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-TableDefs,acentralplacefortableandcolumnnames"/}}TableDefs, a central place for table and column names ===
146 146  
188 +You may have notice the usage of {{code language="none"}}TableDefs.*{{/code}} members.
189 +
190 +Table and column names should never be re-typed everywhere as literals, it is highly recommended to use constants.
191 +
192 +Putting these constants in a dedicated class, say {{code language="none"}}TableDef{{/code}}, allows to use this as an easily accessible list of all tables and columns in the database.
193 +
194 +This is an example:
195 +
196 +{{code language="java"}}
197 +package foo.schema;
198 +
199 +public class TableDefs {
200 +
201 + // It is adviseable to provide the Strings used as names for tables and columns as constants,
202 + // so they can be reused savely to construct SQL statements
203 + 
204 + // 0.1.00
205 + public static final String TABLENAME_ADDRESSBOOK = "ADDRESSBOOK";
206 + public static final String COL_ADDRESSBOOK_ID = "ID";
207 + public static final String COL_ADDRESSBOOK_NAME = "NAME";
208 + public static final String COL_ADDRESSBOOK_ADDRESS_REF = "ADDRESS";
209 + public static final String COL_ADDRESSBOOK_BIRTHDAY = "BIRTHDAY";
210 + // 0.1.01
211 +public static final String COL_ADDRESSBOOK_GENDER = "GENDER";
212 + 
213 +}
214 +{{/code}}
215 +
216 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Triggeringthecreationoftheinitialschema"/}}Triggering the creation of the initial schema ===
217 +
218 +(% style="font-size: 10.0pt;line-height: 13.0pt;" %)To trigger the creation of the initial schema when coming across an empty database, (% style="font-size: 10.0pt;line-height: 13.0pt;" %){{code language="none"}}InitialSchema.getSchema(){{/code}} has to be injected into (% style="font-size: 10.0pt;line-height: 13.0pt;" %){{code language="none"}}SchemaManager.setBaseTables(){{/code}} before calling (% style="font-size: 10.0pt;line-height: 13.0pt;" %){{code language="none"}}SchemaManager.start(){{/code}}.
219 +
147 147  Using Blueprint/Spring, you can do this by inserting the following snippet in the bean definition for SchemaManager:
148 148  
149 149  {{code language="html/xml"}}
150 -<!-- SchemaManager bean definition starts here ... -->
223 +<bp:bean id="initialSchema" class="foo.schema.InitialSchema"></bp:bean>
224 + 
151 151  <bp:property name="baseTables">
152 -<bp:bean factory-ref="tableDefinitions" factory-method="getSetup" />
226 +<bp:bean factory-ref="initialSchema" factory-method="getSchema" />
153 153  </bp:property>
154 -<!-- ... and continues here -->
228 +
155 155  {{/code}}
156 156  
157 157  = {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-UpdatingadatabaseschemawithISchemaUpdateSnippet"/}}Updating a database schema with ISchemaUpdateSnippet =
... ... @@ -161,7 +161,7 @@
161 161  An example for an implementation of a schema update snippet could look like this:
162 162  
163 163  {{code language="java"}}
164 -package org.clazzes.example.jdbc2xml.updates;
238 +package foo.schema;
165 165  
166 166  import java.sql.SQLException;
167 167  import java.sql.Types;
... ... @@ -172,15 +172,11 @@
172 172  import org.clazzes.jdbc2xml.schema.PrimaryKeyInfo;
173 173  import org.clazzes.jdbc2xml.schema.TableInfo;
174 174  
175 -public class SchemaUpdate0_1_01 implements ISchemaUpdateSnippet {
249 +public class SchemaUpdate_0_1_01 implements ISchemaUpdateSnippet {
176 176   
177 177  // This is only accessed through the getter
178 178  private static final String TARGET_VERSION = "0.1.01";
179 179   
180 -// Here it is also adviseable to define constants for reuse in statements.
181 -public static final String COL_EXAMPLE_GENDER = "GENDER";
182 -
183 -
184 184  @Override
185 185  public String getTargetVersion() {
186 186  return TARGET_VERSION;
... ... @@ -188,13 +188,13 @@
188 188  
189 189  @Override
190 190  public String getUpdateComment() {
191 -return "Adding column "+COL_EXAMPLE_GENDER+" to table "+TableDefinitions.TB_EXAMPLE_TABLE_NAME+".";
261 +return "Adding column "+TableDefs.COL_ADDRESSBOOK_GENDER+" to table "+TableDefs.TABLENAME_ADDRESSBOOK+".";
192 192  }
193 193  
194 194  @Override
195 195  public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
196 -TableInfo ti = schemaEngine.fetchTableInfo(TableDefinitions.TB_EXAMPLE_TABLE_NAME, null);
197 - schemaEngine.addColumn(ti, new ColumnInfo(COL_EXAMPLE_GENDER, Types.VARCHAR, 1, null, true, null));
266 +TableInfo ti = schemaEngine.fetchTableInfo(TableDefs.TABLENAME_ADDRESSBOOK, null);
267 +schemaEngine.addColumn(ti, new ColumnInfo(TableDefs.COL_ADDRESSBOOK_GENDER, Types.VARCHAR, 1, null, true, null));
198 198  }
199 199  }
200 200  
... ... @@ -201,7 +201,7 @@
201 201  
202 202  {{/code}}
203 203  
204 -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.
274 +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 ADDRESSBOOK table created via the InitialSchema class above.
205 205  
206 206  To add an entire table you would use the {{code language="none"}}ISchemaEngine.createTable(){{/code}} method, like this:
207 207  
... ... @@ -210,12 +210,12 @@
210 210  public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
211 211   TableInfo tiGroup = new TableInfo(TB_GROUP);
212 212   tiGroup.setColumns(Arrays.asList(new ColumnInfo[] {
213 - new ColumnInfo(TableDefinitions.COL_ID, Types.VARCHAR, 36, null, false, null),
214 - new ColumnInfo(TableDefinitions.COL_NAME, Types.VARCHAR, 100, null, false, null),
215 - new ColumnInfo(TableDefinitions.COL_DESCRIPTION, Types.VARCHAR, 512, null, true, null)
283 + new ColumnInfo(TableDefs.COL_ID, Types.VARCHAR, 36, null, false, null),
284 + new ColumnInfo(TableDefs.COL_NAME, Types.VARCHAR, 100, null, false, null),
285 + new ColumnInfo(TableDefs.COL_DESCRIPTION, Types.VARCHAR, 512, null, true, null)
216 216   }));
217 - tiGroup.setPrimaryKey(new PrimaryKeyInfo(PK_GROUP, TableDefinitions.COL_ID));
218 - tiGroup.setIndices(Arrays.asList(new IndexInfo(IDX_GROUP_01, TableDefinitions.COL_NAME, true, null)));
287 + tiGroup.setPrimaryKey(new PrimaryKeyInfo(PK_GROUP, TableDefs.COL_ID));
288 + tiGroup.setIndices(Arrays.asList(new IndexInfo(IDX_GROUP_01, TableDefs.COL_NAME, true, null)));
219 219  
220 220  schemaEngine.createTable(tiGroup, true);
221 221  }
... ... @@ -226,7 +226,7 @@
226 226  {{code language="java"}}
227 227  @Override
228 228  public void performUpdate(ISchemaEngine schemaEngine) throws SQLException {
229 - String sql = "UPDATE "+TableDefinitions.TB_EXAMPLE_TABLE_NAME+" SET "+TableDefinitions.COL_EXAMPLE_NAME+"=?";
299 + String sql = "UPDATE "+TableDefs.TB_EXAMPLE_TABLE_NAME+" SET "+TableDefs.COL_EXAMPLE_NAME+"=?";
230 230  
231 231   PreparedStatement ps = schemaEngine.getConnection().prepareStatement(sql);
232 232  
... ... @@ -249,14 +249,48 @@
249 249  <!-- ... and continues here -->
250 250  {{/code}}
251 251  
252 -
322 += {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-SchemaMaintainanceStrategies"/}}Schema Maintainance Strategies =
253 253  
254 -
324 +The JDBC2XML Schema management tools allow for 2 different strategies:
255 255  
256 -
326 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Frozen(Initial)TableList"/}}Frozen (% style="font-size: 14.0pt;" %)(Initial) Table List(%%) ===
257 257  
258 -
328 +The legacy strategy is:
259 259  
260 -
330 +(% style="list-style-type: square;" %)
331 +* At the start of a project, create and use {{code language="none"}}InitalSchema.java{{/code}}
332 +* After the first commit, {{code language="none"}}InitalSchema{{/code}} are considered frozen, all changes go into {{code language="none"}}SchemaUpdates{{/code}}, up to one update per source code commit
261 261  
262 -
334 +Advantage: Rock solid.
335 +
336 +Disadvantage: No place to look for the complete and exact current scheme, except actual databases. {{code language="none"}}TableDefs.java{{/code}} provide some information, but may become confusing in the long term.
337 +
338 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Possiblebutdangerous:Evolving(Initial)TableList"/}}Possible but dangerous: Evolving (Initial) Table List ===
339 +
340 +To keep the (Initial) Schema up do date, one might use this strategy:
341 +
342 +(% style="list-style-type: square;" %)
343 +* keep the {{code language="none"}}InitalSchema{{/code}} up to date, so an empty database always gets the current scheme in one shot
344 +* {{code language="none"}}SchemaUpdates{{/code}} are only applied to existing databases
345 +
346 +Advantage: Immediate overview over exact current scheme.
347 +
348 +Disadvantage: Very real danger of messing something up, because
349 +
350 +(% style="list-style-type: square;" %)
351 +* schema updates have to be coded in 2 different places in 2 different ways
352 +* the bean definition has to be maintained in 2 places but just 1
353 +
354 +Conclusion: **DO NOT DO THIS**. This strategy may be ok in very early stages, but at some point it has to be
355 +
356 +=== {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-Recommendation:FreezeInitialTableDefinitionnotlaterthanthefirstReleaseCandidate(RC)"/}}(% style="font-size: 14.0pt;" %)Recommendation: Freeze Initial Table Definition not later than the first Release Candidate (RC)(%%) ===
357 +
358 +It may be ok to start a new project using a fast changing (% style="font-size: 10.0pt;line-height: 13.0pt;" %)(Initial) Table List.
359 +
360 +(% style="font-size: 10.0pt;line-height: 13.0pt;" %)But, please, freeze it at some point. Once the first test server is setup up, internally or at a friendly customer, the Frozen Initial Table List Strategy is the only valid one!
361 +
362 += {{id name="HowTocreateandupdateDatabasesusingSchemaManagerandSchemaUpdateSnippets-RealworldExample"/}}Real world Example =
363 +
364 +This HowTo is currently evolving while an additional developer gets acostumed to the SchemaEngine, for developing [[SDS' org.clazzes.sds.impl.schema package>>url:http://svn.clazzes.org/svn/sds/trunk/sds.impl/src/main/java/org/clazzes/sds/impl/schema||style="font-size: 10.0pt;line-height: 13.0pt;" shape="rect"]](% style="font-size: 10.0pt;line-height: 13.0pt;" %) which is **work in progress**!
365 +
366 +(% style="font-size: 10.0pt;line-height: 13.0pt;" %)\\
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -656824
1 +656798
URL
... ... @@ -1,1 +1,1 @@
1 -https://clazzes.atlassian.net/wiki/spaces/JDBC2XML/pages/656824/How To create and update Databases using SchemaManager and SchemaUpdateSnippets
1 +https://clazzes.atlassian.net/wiki/spaces/JDBC2XML/pages/656798/How To create and update Databases using SchemaManager and SchemaUpdateSnippets