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 "Eric Cournarie (JIRA)" <em...@incubator.apache.org> on 2011/04/08 11:41:05 UTC
[jira] [Created] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
Posted by "Francis De Brabandere (Updated) (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-106:
-------------------------------------------
Fix Version/s: (was: empire-db-2.2.0-incubating)
empire-db-2.2.1-incubating
> 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
> Fix For: empire-db-2.2.1-incubating
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere reassigned EMPIREDB-106:
----------------------------------------------
Assignee: Francis De Brabandere
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-106:
-------------------------------------------
Description:
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.
was:
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.
Fix Version/s: empire-db-2.2.0-incubating
> 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
> Fix For: empire-db-2.2.0-incubating
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
Posted by "Francis De Brabandere (Updated) (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-106:
-------------------------------------------
Fix Version/s: (was: empire-db-2.3.0)
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (EMPIREDB-106) createDatabase should not try to
create schemas in the DDL script if database name has not been set
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017365#comment-13017365 ]
Francis De Brabandere commented on EMPIREDB-106:
------------------------------------------------
Makes sense, somehow related to EMPIREDB-101 and EMPIREDB-104
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira