Hi all, I was excited to find out 1.2 was released and tried to upgrade my sandbox environment from 1.1 today. I already had 1.1 deployed as a Wildlfly module, and extracted the 1.2 overlay edition along with the 1.2 Wildfly adapter. The database update was chugging along fine for a bit, but did hit an error. It seems to be an SQL dialect problem. Because of company policies, I’m forced to use MS SQL, and am using the JDBC 41 driver deployed as a Wildfly module. I’ve attached the relevant log output, starting from the beginning of the database update. I did take a DB backup before starting, so I can restore and replicate the update process from the beginning again. Could you please take a look and let me know what I can do? Thanks, John _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

Thanks Marek. I created KEYCLOAK-1336. I’m using the free SQL Server Express 2008 R2 in my sandbox, but the same issue should exist in any MS SQL Server version as it handles Booleans differently than most other RDBMS’. John *From:* Marek Posolda [mailto:mposolda@redhat.com] *Sent:* Thursday, May 21, 2015 2:23 AM *To:* Schneider, John DODGE CONSULTING SERVICES, LLC; keycloak-user(a)lists.jboss.org *Subject:* [External] Re: [keycloak-user] Error upgrading MS SQL database from 1.1 Final to 1.2 Final Hi, This looks like a bug, it seems that MS SQL server doesn't know what the 'true' is, so the SQL statement used here https://github.com/keycloak/keycloak/blob/master/connections/jpa-liquibas... is failing :-( Could you create JIRA for it please? Btv. which version of MS SQL server are you using? Thanks, Marek On 20.5.2015 20:16, Schneider, John DODGE CONSULTING SERVICES, LLC wrote: Hi all, I was excited to find out 1.2 was released and tried to upgrade my sandbox environment from 1.1 today. I already had 1.1 deployed as a Wildlfly module, and extracted the 1.2 overlay edition along with the 1.2 Wildfly adapter. The database update was chugging along fine for a bit, but did hit an error. It seems to be an SQL dialect problem. Because of company policies, I’m forced to use MS SQL, and am using the JDBC 41 driver deployed as a Wildfly module. I’ve attached the relevant log output, starting from the beginning of the database update. I did take a DB backup before starting, so I can restore and replicate the update process from the beginning again. Could you please take a look and let me know what I can do? Thanks, John _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user