[
https://issues.apache.org/jira/browse/IMAP-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893741#action_12893741
]
Eric Charles commented on IMAP-181:
-----------------------------------
Tks for your feedback Tim.
I corrected the typo.
I wouldn't omit IMAP because you can also have JAMES-...
About the jira interval, I thought to introduce some dependencies (say for
example IMAP-168 before IMAP-165). The migration must sometimes respect an
order which is not necessarily a numeric order.
We could also extend the requirement to 'upgrade db schema to version x", where
x wouldn't necessarily nor follow the james release. This would allow easier
database migration between releases (say for developers deploying trunk with
real users).
But we also have to take care to not re-develop existing tools (such as
http://www.liquibase.org/) and to monitor the jpa evolution on schema
synchronization.
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
