You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "jan (JIRA)" <em...@incubator.apache.org> on 2015/03/30 14:05:52 UTC

[jira] [Updated] (EMPIREDB-217) Consistency check for data model defintion vs deployed data model

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

jan updated EMPIREDB-217:
-------------------------
    Attachment: Empire-db Check.zip

The initial version of the DB consistency check.

Some code and inspiration was taken from the CodeGenParser class. 

The class EmpireDBCheck features a main method that should be self-explained.

There is an open TODO in OracleDBModelChecker - the BooleanType should come from the chosen DBDriver.

Hope this is useful for you.

> Consistency check for data model defintion vs deployed data model
> -----------------------------------------------------------------
>
>                 Key: EMPIREDB-217
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-217
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rainer Döbele
>         Attachments: Empire-db Check.zip
>
>
> Suggestion from Jan on the user mailing list:
> I want to validate the consistency of my DB schema against my empire-db schema on application startup.
>  
> It would be nice to be able to check:
>  
> - Tables (names, primary keys)
> - Columns (names, data types, size)
> - Existence foreign keys
> - Existence of indexes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)