[
https://issues.apache.org/jira/browse/EMPIREDB-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541918#comment-14541918
]
ASF GitHub Bot commented on EMPIREDB-217:
-----------------------------------------
GitHub user jan666 opened a pull request:
https://github.com/apache/empire-db/pull/1
Improved checking of foreign keys
See Rainers comment on https://issues.apache.org/jira/browse/EMPIREDB-217
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jan666/empire-db master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/empire-db/pull/1.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1
----
commit 80bf0b5503e41d32df9a9be13751bbe919010031
Author: jan <[email protected]>
Date: 2015-05-13T13:30:51Z
improved checkForeignKeys
commit eb3c91179eb21a33f3c4a0b52f2d3b10cfdaff56
Author: jan <[email protected]>
Date: 2015-05-13T13:33:15Z
improved checkForeignKeys
----
> 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 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)
