[
https://issues.apache.org/jira/browse/JAMES-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139010#comment-17139010
]
Benoit Tellier commented on JAMES-2586:
---------------------------------------
> We also have github and this creates duplication and we should discuss this
> in another thread.
In my opinion github should be limited to reviewing code. So I see little
overlap.
> I think ideas should be discussed on the mailing list.
+1
I just want to add nuance. Browsing mailing list to retrieve things could be
harder than JIRA tickets where you can link things together, rely on
components, label things, etc...
Maybe the right thing to do is leverage our tooling to allow both of your goals
to be achievable.
Maybe we could introduce a 'label' for long term propositions that could easily
be filtered in & out ?
> 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
