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

Posted to dev@eagle.apache.org by "Hao Chen (JIRA)" <ji...@apache.org> on 2016/03/16 06:25:33 UTC

[jira] [Resolved] (EAGLE-190) JBDC Metadata Storage Extension

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

Hao Chen resolved EAGLE-190.
----------------------------
    Resolution: Fixed

> JBDC Metadata Storage Extension
> -------------------------------
>
>                 Key: EAGLE-190
>                 URL: https://issues.apache.org/jira/browse/EAGLE-190
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.3.0
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>             Fix For: v0.3.0
>
>
> JDBC as metadata storage maybe more convenient and light-weight for user to use.
> * Support Derby in Memory: The JDBC can support derby and mysql completely, and use derby in memory by default, so that user don’t have to install any additional dependencies even mysql to get started, and also our unit test could easily pass without any tricky modifications.
> * Automatic DDL Schema Manager: JdbcEntitySchemaManager could automatically create all required tables if not existing when application is started.
> * Fixed JDBC reserved field name like desc, group and so on
> * Force update while inserting failed due to duplicated key exception



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