[
https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139945#comment-17139945
]
Matthieu Baechler commented on JAMES-2586:
------------------------------------------
I don't have opinion about whether we should use JIRA or a mailing list to
discuss ideas: it looks like both work currently.
What do we gain at restricting usage to only one of them? And then, who will
enforce the choice?
Eugen, you said using JIRA to keep ideas and/or mid/long term goals interferes
with the project management part: my argument is that filtering on milestone
solves that issue and you didn't answered, as far as I understand.
Of course I want to reach a global agreement and I don't care that things stay
as they are or fit my habits. Community comes first. Thank your for bringing
this debate.
> Implement a Postgres-specific backend
> -------------------------------------
>
> Key: JAMES-2586
> URL: https://issues.apache.org/jira/browse/JAMES-2586
> Project: James Server
> Issue Type: New Feature
> Reporter: Matthieu Baechler
> Priority: Major
>
> James has a JPA implementation of most interfaces that allows to deploy it on
> top of some popular RDBMS.
> However, while useful for some kind of applications, ORM are usually a bad
> fit for applications requiring high performance like a mail server.
> As an abstraction, it also prevents from using advanced features of a given
> RDBMS.
> For most usages, James would probably run great on top of Postgres, given
> that we use advanced features to implement search, for example.
> A good strategy would be to implement all interfaces implemented by JPA with
> a modern Postgres driver.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
