[
https://issues.apache.org/jira/browse/MAILBOX-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025653#comment-13025653
]
Eric Charles commented on MAILBOX-61:
-------------------------------------
Currently, if 1 messages is copied, JPA considers that one entry in mailbox is
enough, and creates as many mailboxmembership as copies.
I suppose we will have to create two rows in JAMES_MESSAGE table if we merge. I
don't see any problem with this, just a simple check to see if this will be the
case.
Do we really need migration scripts? We are still in milestone phase. Maybe we
should ask in a separate thread on mailing list.
An alternative to avoid SQL migration scripts would be to copy jpa-mailbox to
maildir-mailbox, recreate database and recopy maildir-mailbox to jpa-mailbox.
I made this sometime ago and was more happy that having to apply long running
SQL scripts. Going to SQL has also a risk to deal with database specifies.
> Merge MailboxMembership and Message interfaces and implementation
> -----------------------------------------------------------------
>
> Key: MAILBOX-61
> URL: https://issues.apache.org/jira/browse/MAILBOX-61
> Project: James Mailbox
> Issue Type: Task
> Components: jcr mailbox, jpa mailbox, maildir mailbox, store
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.2
>
>
> At the moment we have the MailboxMembership and the Message interfaces to
> represend a Message which is stored in a Mailbox. This makes things more
> complex as they should be without any gain. We should better merge this two
> interfaces and the implementations.
> Special care need to get taken for the JPA implementation as we need some
> kind of "migration script" here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
