Yes, I am seeing it too. It shouldn't
affect any functionality. Whole testsuite is passing fine with
MySQL inspite of those warnings. Or do you see some other
consequences?
But possibly there might be some uncleaned objects in schema
(indexes, constraints, etc) from tables, which were dropped during
migration. I don't have idea if it's the case or not. Maybe we
should investigate and doublecheck this? Feel free to create JIRA
for that.
Marek
On 25.6.2015 12:34, Matthias Wessendorf wrote:
Hi,
I did run KC 1.3.1 w/ latest Docker image (5.6) on EAP 6.4,
and I am getting this warning:
10:50:55,579 WARN
[org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider]
(ServerService Thread Pool -- 72) Database does not support
drop with cascade
Did anyone notice - or try - this too?
--
_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev