empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Resolved] (EMPIREDB-106) createDatabase should not try to create schemas in the DDL script if database name has not been set
Date Mon, 04 Feb 2013 13:54:13 GMT

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

Rainer Döbele resolved EMPIREDB-106.
------------------------------------

    Resolution: Fixed

This issue should have been resolved already.
Probably the issue status has not been updated.
MSSQL and MySQL will only try to create the database if the name is given.

                
> createDatabase should not try to create schemas in the DDL script if database name has
not been set
> ---------------------------------------------------------------------------------------------------
>
>                 Key: EMPIREDB-106
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-106
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.1.0-incubating
>            Reporter: Eric Cournarie
>            Assignee: Francis De Brabandere
>
> Some drivers (MySQL and MSSQL) are trying to create the schema in the DDL. I think this
is useless, as most of the time, the schema needs to be created to be able to access the database.

> If the databaseName has not been set, the DDL should not contain create schema statement
but just the create tables, relations and views. Other Empire drivers (Oracle for instance)
are not doing schema creation in the DDL, not sure to 
> understand why this is done for MySQL and MS SQL Server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message