Kodo 3.0 migrator does not honor metadata table/column names

Question

it outputs <field_name>X instead completely disregarding what's in the
metadata

Answer 1

Ok running it on classess enhanced with 2.5.2 produces bad names, while
runnung it on unenhanced classed works all right
<mapping>
<package name="peacetech.nci.cs.jdo">
<class name="Contract">
<jdbc-class-map type="base" table="CONTRACTX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="currentModification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_CURRENTMODIFICATIOX"
column.MODIFICATIONIDX="MODIFICATIONID_CURRENTMODIFICX"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="IDX"/>
</field>
<field name="lastModification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_LASTMODIFICATIONX"
column.MODIFICATIONIDX="MODIFICATIONID_LASTMODIFICATIX"/>
</field>
<field name="modifications">
<jdbc-field-map type="many-many"
element-column.CONTRACTIDX="CONTRACTID_MODIFICATIONSX"
element-column.MODIFICATIONIDX="MODIFICATIONID_MODIFICAT
IONSX" ref-column.IDX="ID_JDOIDX" table="CONTRACT_MODIFICATIONSX"/>
</field>
</class>
<class name="Modification">
<jdbc-class-map type="base" table="MODIFICATIONX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="approved">
<jdbc-field-map type="value" column="APPROVEDX"/>
</field>
<field name="contract">
<jdbc-field-map type="one-one" column.IDX="ID_CONTRACTX"/>
</field>
<field name="contractId">
<jdbc-field-map type="value" column="CONTRACTIDX"/>
</field>
<field name="description">
<jdbc-field-map type="value" column="DESCRIPTIONX"/>
</field>
<field name="modificationId">
<jdbc-field-map type="value" column="MODIFICATIONIDX"/>
</field>
<field name="obligations">
<jdbc-field-map type="many-many"
element-column.IDX="ID_OBLIGATIONSX"
ref-column.CONTRACTIDX="CONTRACTID_JDOIDX" ref-column.MODIFICATIONIDX="MOD
IFICATIONID_JDOIDX" table="MODIFICATION_OBLIGATIONSX"/>
</field>
</class>
<class name="Obligation">
<jdbc-class-map type="base" table="OBLIGATIONX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="amount">
<jdbc-field-map type="value" column="AMOUNTX"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="IDX"/>
</field>
<field name="modification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_MODIFICATIONX"
column.MODIFICATIONIDX="MODIFICATIONID_MODIFICATIONX"/>
</field>
</class>
</package>
</mapping>
running on unenhanced classes produces proper metadata (as far as names
concerned)
<?xml version="1.0" encoding="UTF-8"?>
<mapping>
<package name="peacetech.nci.cs.jdo">
<class name="Contract">
<jdbc-class-map type="base" table="CONTRACT"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="currentModification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"
column.MODIFICATION_ID="CURRENT_MODIFICATION_ID"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="CONTRACT_ID"/>
</field>
<field name="lastModification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"
column.MODIFICATION_ID="LAST_MODIFICATION_ID"/>
</field>
<field name="modifications">
<jdbc-field-map type="one-many"
ref-column.CONTRACT_ID="CONTRACT_ID" table="MODIFICATION"/>
</field>
</class>
<class name="Modification">
<jdbc-class-map type="base" table="MODIFICATION"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="approved">
<jdbc-field-map type="value" column="IS_APPROVED"/>
</field>
<field name="contract">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"/>
</field>
<field name="contractId">
<jdbc-field-map type="value" column="CONTRACT_ID"/>
</field>
<field name="description">
<jdbc-field-map type="value" column="DESCRIPTION"/>
</field>
<field name="modificationId">
<jdbc-field-map type="value" column="MODIFICATION_ID"/>
</field>
<field name="obligations">
<jdbc-field-map type="one-many"
ref-column.CONTRACT_ID="CONTRACT_ID"
ref-column.MODIFICATION_ID="MODIFICATION_ID" table="OBLIGATION"/>
</field>
</class>
<class name="Obligation">
<jdbc-class-map type="base" table="OBLIGATION"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="amount">
<jdbc-field-map type="value" column="AMOUNT"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="OBLIGATION_ID"/>
</field>
<field name="modification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID" column.MODIFICATION_ID="MODIFICATION_ID"/>
</field>
</class>
</package>
</mapping>
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
Yes; see
http://solarmetric.com/Software/beta/3.0.0/b1-docs/docs/ref_guide_mapping_factory.html
for descriptions of the various options.
The three basic ways to store mapping information are: in metadata
extensions, in the database, and in separate .mapping files. IMO, storing
in separate .mapping files is the best -- storing the info in metadata
makes your metadata get really ugly, and storing it in the db makes it
relatively hard to modify (at least, until we release our GUI tool...)
-Patrick
On Mon, 04 Aug 2003 19:38:16 -0400, Alex Roytman wrote:
can mapping files be used as an alternative to jdo extensions to
complement standard jdo metadata or it is strictly for mapping tool? in
other words can I have a standard jdo metadata with no extensions plus a
mapping file to replace jdo metadata with extensions if yes, what is
your primary format two file (jdo + mapping file) or one file jdo with
extensions--
Patrick Linskey
SolarMetric Inc.
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
Can you post the command that you used to run the conversion? I just ran
through the conversion process for a small (10 tables or so) schema
earlier today with no problems.
-Patrick
On Mon, 04 Aug 2003 19:31:06 -0400, Alex Roytman wrote:
it outputs <field_name>X instead completely disregarding what's in the
metadata--
Patrick Linskey
SolarMetric Inc.