[
https://issues.apache.org/jira/browse/MAILBOX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed MAILBOX-8.
--------------------------------
Resolution: Fixed
3.0 is a long time behind us...
> Implement database schema and data incremental migration for 3.0 release
> ------------------------------------------------------------------------
>
> Key: MAILBOX-8
> URL: https://issues.apache.org/jira/browse/MAILBOX-8
> Project: James Mailbox
> Issue Type: New Feature
> Components: jpa
> Environment: all
> Reporter: Eric Charles
> Priority: Major
> Attachments: jpa-migrator-2.zip, jpa-migrator-3.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 was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
