Create Groovy DSL for jcatapult-dbmgr.

GoogleCodeExporter commented 8 years ago

Example of an issue that needs resolution:
Assume component A has version 1.0 and 1.1. Component A renames a column in 
1.1.  Component 
B currently depends on version 1.0.  Component B inserts a row into a component 
A 1.0 table.  
When component B upgrades to component A 1.1, the component B insert statement 
will fail 
because component A 1.1 renamed the column.  This occurs because dbmgr creates 
database 
tables for each component across all versions of that component before moving 
on to the next 
component in the depth-first ordered list.  The DSL will provide the capability 
to specify which 
version of a component's table an insert statement is targeted towards.

Original issue reported on code.google.com by leafkn...@gmail.com on 8 Jan 2008 at 10:04

GoogleCodeExporter commented 8 years ago

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 3:23

Added labels: Component-Ant, OpSys-All

GoogleCodeExporter commented 8 years ago

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 3:24

Added labels: Milestone-1.1

GoogleCodeExporter commented 8 years ago

Original comment by bpontare...@gmail.com on 18 Mar 2008 at 4:18

Letractively / jcatapult

Create Groovy DSL for jcatapult-dbmgr. #2