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] Updated: (DDLUTILS-188) Add multiple schema support
Date Mon, 03 Nov 2008 23:52:44 GMT

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

Thomas Dudziak updated DDLUTILS-188:
------------------------------------

    Fix Version/s: 1.2

> Add multiple schema support
> ---------------------------
>
>                 Key: DDLUTILS-188
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-188
>             Project: DdlUtils
>          Issue Type: Improvement
>          Components: Core (No specific database), Core - PostgreSql
>         Environment: all
>            Reporter: Jon Keys
>            Assignee: Thomas Dudziak
>             Fix For: 1.2
>
>         Attachments: ddlutils-multischema.patch
>
>
> As mentioned in issue 116 there was no support for multiple schemas.
> This patch adds initial support against the latest svn head (603834).
> Features added in this patch include:
>     - support for schema definition in xml schema definition document
>     - ability to create / drop multiple schemas in a single database (yes, even from
ant)
>     - support for object creation / removal in separate schemas (tables, constraints,
sequences, etc...)
>     - support for insert / update / delete operations for separate schemas
>     - support for altering model with multiple schemas
> This multiple schema support was added as a boolean attribute to the PlatformInfo and
is currently only "enabled" for the PostgreSQL platform implementation.
> If you're interested in "enabling" this feature for another platform you should also
override the "createSchemas" and "dropSchemas" methods in the specific platform's SqlBuilder
implementation.
> Also added in this patch:
>     - ObjectStor class which can serialize a java object to a byte array and un-serialize
an existing byte array back to a java object
> This class is useful when the platform isn't able to deal directly with the JAVA_OBJECT
type.
> I used this in setObject method of the PostgreSqlPlatform class when the type is a JAVA_OBJECT
because the PostgreSQL jdbc driver is unable to deal directly with java objects (it stores
the serialized object instead).

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


Mime
View raw message