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 "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2015/06/18 11:13:00 UTC

[jira] [Resolved] (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 ]

Rainer Döbele resolved EMPIREDB-217.
------------------------------------
       Resolution: Fixed
    Fix Version/s: empire-db-2.4.4
         Assignee: Rainer Döbele

Feature works well.
Thank you Jan for that great piece of work!


> 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
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.4.4
>
>         Attachments: Empire-db Check v0.2.zip, 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)