You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Jira)" <se...@james.apache.org> on 2020/06/17 14:26:01 UTC

[jira] [Resolved] (JAMES-2660) Sample mariadb jpa file is wrong

     [ https://issues.apache.org/jira/browse/JAMES-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioan Eugen Stan resolved JAMES-2660.
------------------------------------
      Assignee: Benoit Tellier
    Resolution: Fixed

Merged via Github.

> Sample mariadb jpa file is wrong
> --------------------------------
>
>                 Key: JAMES-2660
>                 URL: https://issues.apache.org/jira/browse/JAMES-2660
>             Project: James Server
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 3.2.0
>            Reporter: Simon Levesque
>            Assignee: Benoit Tellier
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> File server/container/guice/jpa-smtp-mariadb/sample-configuration/james-database.properties
> Currently:
> {code:java}
> # Supported adapters are:
> # DB2, DERBY, H2, HSQL, INFORMIX, MYSQL, ORACLE, POSTGRESQL, SQL_SERVER, SYBASE 
> vendorAdapter.database=mariaDB
> {code}
> *mariaDB* is not a valid value per the comment, but also per *EclipseLinkJpaVendorAdapter* and *OpenJpaVendorAdapter*
> Normally, *MYSQL* should do the trick for mariadb.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org