Hello,
I guess that is finally a bug: this is related with the version of the
DB/JDBC connector used.
We entered into the logs and we saw that there are several errors for
"table not found": this is due to the fact that the tables are declared
in uppercase, while are stored in Lowercase into the database. Per
construction of some DB/JDBC, MariaDB distinguishes also the case
sensitivity of the tables names, so the tables are marked as "not found".
Just as an experiment, we changed by hand the table names and now looks
working.
Hope that helps and thanks for the support
On 11/04/17 15:37, Fabio Martelli wrote:
Hi, it seems it was not a real bug. If you are on linux, pay attention
to the default character encoding "character-set-server": utf8mb4 is
not compatible with Apache Syncope >2.0.3.
BTW, I think your DataIntegrityViolation is not due to the problem above.
I've just been able to replicate your issue by using MariaDB 10.0 and
Java connector 1.5.9.
It seems that there are a sort of incompatibility that affect certain
insert statement.
I solved the problem by changing the java connector version: MariaDB
10.0 and JConnector 1.4.6 seem to work fine together.
Please, find your compatible versions, drop and recreate your db and
check it out again.
Best regards,
F.
Il 10/04/2017 16:50, Fabio Martelli ha scritto:
Hi, it seems we have a bug.
See the issue [1]; it will be solved ASAP.
Thank you for reporting.
Regards,
F.
[1] https://issues.apache.org/jira/browse/SYNCOPE-1065
Il 10/04/2017 12:35, Tech ha scritto:
Dear experts,
We are working with the Syncope 2.0.3-SNAPSHOT, we are doing nothing
but changing the default database, from Postgres to MariaDB.
We compile and we start a brand new Syncope deployment with a new
empty database.
We are able to create users, but we every time we try to create a
new Type, we get an error "DataIntegrityViolation [The transaction
has been rolled back.." and we cannot add any other type.
Have you any idea why this could happen?
