You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tim-Christian Mundt (JIRA)" <se...@james.apache.org> on 2010/07/29 16:53:18 UTC

[jira] Commented: (IMAP-181) Implement database schema and data incremental migration for 3.0 release

    [ https://issues.apache.org/jira/browse/IMAP-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893642#action_12893642 ] 

Tim-Christian Mundt commented on IMAP-181:
------------------------------------------

Eric, I didn't test, but read through your code and it looks good. I don't think the SQL should cause any problem, because it's not really specialized. Maybe you could introduce a little convenience: "jpa-migrator 165-180" would be equivalent to "jpa-migrator 165 168 172 176 180" (I'd omit the "IMAP").

Thanks for this handy tool.

> Implement database schema and data incremental migration for 3.0 release
> ------------------------------------------------------------------------
>
>                 Key: IMAP-181
>                 URL: https://issues.apache.org/jira/browse/IMAP-181
>             Project: JAMES Imap
>          Issue Type: New Feature
>          Components: JPA Mailbox
>         Environment: all
>            Reporter: Eric Charles
>            Assignee: Eric Charles
>         Attachments: jpa-migrator-2.zip, jpa-migrator.zip
>
>
> We need a way to upgrade the database (for JPA store) whenever it is needed.
> In general, a database upgrade is needed further a JIRA that impacts the database.
> This can be:
> 1. On a db schema level (table, columns, fk, index,...)
> 2. On data level (update some data, feed a column with relation keys,...).
> Plain SQL would be enough for the first point (not for the second one). PLSQL (or similar) would be needed for the second point.
> To ease things, a java "software" process will developed based on the existing JPA layer.
> The tool should be invoked with JIRA numbers as parameters.
> Each provided JIRA number would invoke a DB Change Command.
> As POC (Proof of Concept), we will first develop a tool that takes into account.
> - https://issues.apache.org/jira/browse/IMAP-176
> - https://issues.apache.org/jira/browse/IMAP-172
> - https://issues.apache.org/jira/browse/IMAP-168
> - https://issues.apache.org/jira/browse/IMAP-165

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


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org