db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-201) Reading a model from MS SQL Server 2005 only succeeds for tables in the "dbo" schema
Date Mon, 16 Jun 2008 04:15:45 GMT

    [ https://issues.apache.org/jira/browse/DDLUTILS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605193#action_12605193

Thomas Dudziak commented on DDLUTILS-201:

Full support for multiple schemas is covered by DDLUTILS-116, which covers support for e.g.
fully qualified table names and handling multiple different schemas in one database model.
However, DdlUtils already supports catalog and schema specification when reading and writing
models (both API and Ant tasks), it only cannot handle qualified table names. For Sql Server,
I think you have to specify a catalog pattern instead of a schema pattern, but I might be
wrong there.

> Reading a model from MS SQL Server 2005 only succeeds for tables in the "dbo" schema
> ------------------------------------------------------------------------------------
>                 Key: DDLUTILS-201
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-201
>             Project: DdlUtils
>          Issue Type: Bug
>          Components: Core - SqlServer
>    Affects Versions: 1.0
>         Environment: MS SQL Server 2005
>            Reporter: rick cameron
>            Assignee: Thomas Dudziak
> When Platform.readModelFromDatabase is used to read the model of a SQL Server 2005 database,
it fails for tables that are in a schema other than "dbo". 
> There are several places in the code where the schema name should be specified, but is
not. For example, in JdbcModelReader.determineAutoIncrementFromResultSetMetaData the table
name should be qualified by the schema name.
> It's also necessary to change the way indices and primary & foreign keys are read
in DatabaseMetaDataWrapper. Currently the schema pattern is always null. This works for tables
in the "dbo" schema, but not for others.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message