Return-Path: X-Original-To: apmail-empire-db-commits-archive@www.apache.org Delivered-To: apmail-empire-db-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76F4D17271 for ; Mon, 13 Apr 2015 05:47:13 +0000 (UTC) Received: (qmail 39808 invoked by uid 500); 13 Apr 2015 05:47:13 -0000 Delivered-To: apmail-empire-db-commits-archive@empire-db.apache.org Received: (qmail 39789 invoked by uid 500); 13 Apr 2015 05:47:13 -0000 Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: empire-db-dev@empire-db.apache.org Delivered-To: mailing list commits@empire-db.apache.org Received: (qmail 39768 invoked by uid 500); 13 Apr 2015 05:47:12 -0000 Delivered-To: apmail-incubator-empire-db-commits@incubator.apache.org Received: (qmail 39765 invoked by uid 99); 13 Apr 2015 05:47:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2015 05:47:12 +0000 Date: Mon, 13 Apr 2015 05:47:12 +0000 (UTC) From: "jan (JIRA)" To: empire-db-commits@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (EMPIREDB-217) Consistency check for data model defintion vs deployed data model MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/EMPIREDB-217?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] jan updated EMPIREDB-217: ------------------------- Attachment: Empire-db Check v0.2.zip > 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=C3=B6bele > 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 s= chema on application startup. > =20 > It would be nice to be able to check: > =20 > - 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)