[jira] Updated: (DDLUTILS-116) Fully support multiple schemas

["Laurent ROCHE (JIRA)" <ji...@apache.org>]

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

Laurent ROCHE updated DDLUTILS-116:
-----------------------------------

    Attachment: lro.diff

I have made a few fixes to be able to export/import data using schemas (on PostgreSQL), see files included at the end of the post.
Most of them are quite ugly fixes but that works for me  ... and still, they should not interfere with other people usage.

Main problem fixed in included files were:
 - reading a model from XML file (schema is not handled then).
 - INSERT INTO was not prefexing table names with schema name.
 - writeDataToDatabase methods were not handling _determineSchema property.
(neither was writeDataToXML but I fixed that previously - see september post).

I've added a new method in class DatabaseIO:
public Database read(String filename, String schema)
to be able to pass the schema as a parameter.
It's fixed in another way in DdlToDatabaseTask.

If anybody is interested in more explanations, feel free to ask.

Moving forward (in next versions), I would assume that it would be better to add the schema in the XML file produced.
The question is: once in the file (e.g. in the <data> tag)  -that will mean only one schema per file-,
or per table (in each line) - that will mean being able to export the complete database with all schemas.

The diff file applies to version 1.0 not the latest SVN files.

> Fully support multiple schemas
> ------------------------------
>
>                 Key: DDLUTILS-116
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-116
>             Project: DdlUtils
>          Issue Type: Improvement
>          Components: Core (No specific database)
>            Reporter: Thomas Dudziak
>            Assignee: Thomas Dudziak
>            Priority: Critical
>             Fix For: 1.1
>
>         Attachments: lro.diff
>
>
> Multiple schemas in one database should be supported fully in both ways: model (XML with new 'schema' elements/attributes) <-> database that supports multiple schemas

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