empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt DeHoust (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Updated] (EMPIREDB-114) Codegen adds redundant relations to the database model
Date Fri, 02 Sep 2011 16:07:09 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matt DeHoust updated EMPIREDB-114:

    Attachment: codegen-relations-problem-scenario.patch.txt

This patch provides a test case that shows the problem. No solution is proposed. The test
can be improved, but is enough to illustrate the issue.

> Codegen adds redundant relations to the database model
> ------------------------------------------------------
>                 Key: EMPIREDB-114
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-114
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: CodeGenerator
>    Affects Versions: empire-db-2.2.0-incubating
>            Reporter: Matt DeHoust
>         Attachments: codegen-relations-problem-scenario.patch.txt
> Under some circumstances CodeGen produces redundant relations on the DBDatabase, which
may lead to problems if you use the empire-db model to create your schema. The script will
fail when you try to create the same foreign key relationship twice.
> Steps to reproduce:
> 1. Define a schema with at least two different tables with foreign key relationships.
> 2. Use the "dbTablePattern" configuration option.
> 3. The generated DBDatabase will add the same relations more than once.
> This is a major problem if you use empire-db to generate schemas with foreign key relationships.
If not, you can work around the problem by modifying the Database.vm template to exclude the
relations setup..

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message