My next question, as I slowly plow my way through [re-]learning DD.
I've got a DCT which has 2 sections that will store information for the same table in the DB. e.g.:
<column name="foo"
data-type="VARCHAR(50)"
value-from-field="container1/0/container2/0/foo_id"/>
...
<column name="foo"
data-type="VARCHAR(50)"
value-from-field="container1/0/container3/0/foo_id"/>Putting these into two
different groups is clearly
not a problem. Unfortunately, we have need for them to end up in the same table (two sources of the same type of data for one target table in the DB).
Is it allowed to define the same group twice in a dbschema.cfg ?
<group name="FOO_TABLE" root-group="yes">
<attrmap>
<column name="foo" ...data from container2.../>
...
</attrmap>
<keys>
...
</keys>
</group>
...
<group name="FOO_TABLE" root-group="yes">
<attrmap>
<column name="foo" ...data from container3.../>
...
</attrmap>
<keys>
...
</keys>
</group>I.e. will it just process it in a top-down fashion such that it won't care? Or will it try to comprehend the
entire schema at one time and error-out due to two group's with the same name in the same configuration file?
One of the DB guys said they might be able to re-design things to avoid this - but I'd rather not have him do it at this late stage in the project (less than a month to go) as there are a number of other parts of the project utilizing the DB and I'd hate to think of the ripple-effect this kind of change might cause. If we must, we will -- but if we don't have to, I'd rather not.
(hopefully on Monday I'll get to the deployment config file and be able to start testing things out - but I want to get the dbschema.cfg handled first....)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
