Good. Now it works. However the new problem is, the databases are not
identical. I mean the database generated from the XML file has some
differences with the database which generates the XML file. I found the
difference simply by comparing the XML file.
The part of the original XML file.
<table name="Accrual">
<column name="AccrualID" primaryKey="true" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="PeriodFK" primaryKey="false" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="FileName" primaryKey="false" required="true"
type="VARCHAR" size="50" autoIncrement="false"/>
<column name="AccruedByFK" primaryKey="false" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="AccruedOn" primaryKey="false" required="true"
type="TIMESTAMP" size="23" autoIncrement="false"/>
<foreign-key foreignTable="Employee" name="FK_Accrual_Employee">
<reference local="AccruedByFK" foreign="EmployeeID"/>
</foreign-key>
<foreign-key foreignTable="Period" name="FK_Accrual_Period">
<reference local="PeriodFK" foreign="PeriodID"/>
</foreign-key>
<unique name="PK_Accrual">
<unique-column name="AccrualID"/>
</unique>
<index name="IX_Accrual_Employee">
<index-column name="AccruedByFK"/>
</index>
<index name="IX_Accrual_Period">
<index-column name="PeriodFK"/>
</index>
</table>
The new XML file generated from the new database which creates from the
above XML file.
<table name="Accrual">
<column name="AccrualID" primaryKey="true" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="PeriodFK" primaryKey="false" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="FileName" primaryKey="false" required="true"
type="VARCHAR" size="50" autoIncrement="false"/>
<column name="AccruedByFK" primaryKey="false" required="true"
type="NUMERIC" size="8" autoIncrement="false"/>
<column name="AccruedOn" primaryKey="false" required="true"
type="TIMESTAMP" size="23" autoIncrement="false"/>
<foreign-key foreignTable="Employee" name="FK_Accrual_Employee">
<reference local="AccruedByFK" foreign="EmployeeID"/>
</foreign-key>
<foreign-key foreignTable="Period" name="FK_Accrual_Period">
<reference local="PeriodFK" foreign="PeriodID"/>
</foreign-key>
<unique name="PK__Accrual__379B24DB">
<unique-column name="AccrualID"/>
</unique>
<unique name="PK_Accrual">
<unique-column name="AccrualID"/>
</unique>
<index name="IX_Accrual_Employee">
<index-column name="AccruedByFK"/>
</index>
<index name="IX_Accrual_Period">
<index-column name="PeriodFK"/>
</index>
</table>
Look at the hightlighted part. It happened to every table in the database. A
newly added unique constraint.
On 2/9/06, Thomas Dudziak <[EMAIL PROTECTED]> wrote:
>
> On 2/9/06, Jun Li <[EMAIL PROTECTED]> wrote:
>
> > OK, Here is the info.
>
> <snip>
>
> > Here are the exceptions:
> >
> > ........
> >
> > 9/02/2006 09:57:04 org.apache.commons.betwixt.expression.ContextpopOptions
> >
> > INFO: Cannot pop options off empty stack
>
>
> You seem to be running an older version of DdlUtils (this particular
> INFO message comes from an older commons-betwixt version which we
> replaced a couple of weeks ago).
> Could you update DdlUtils to newest SVN and try again ?
>
> Tom
>
