which version of MS-SQL are you using? For me latest keycloak master
works with MS-SQL 2012, but I have to manually change dialect. The
default dialect org.hibernate.dialect.SQLServerDialect , which is
autodetected by Hibernate doesn't work correctly due to columns with
boolean types, I have to change it to use
org.hibernate.dialect.SQLServer2008Dialect . Could you try in your
You can either:
-- Add system property
starting server (In latest keycloak master, system properties could
override what's set in persistence.xml)
-- Add this property to persistence.xml
If you have MS-SQL 2005, you can also try
On 19.2.2014 09:30, Marek Posolda wrote:
Thanks for looking into databases. Right now, Keycloak should work on
MySQL, PostgreSQL, Oracle and Sybase. Still looking on MS-SQL and IBM
DB2 and I've created separate issue KEYCLOAK-303
for it, as it seems
that MS-SQL issue is not related to ID generation. I will reply once I
have luck with MS-SQL, so you can test in your environment.
On 18.2.2014 21:59, Bill Burke wrote:
> RealmEntity's ID is set manually and uses the same code as
> JpaIdGenerator. I think Marek is looking into MSSQL.
> On 2/18/2014 3:49 PM, Dean Peterson wrote:
>> I realize you are still in development for the alpha2 release. Thank
>> you for making the change to UUID rather than Identity String columns.
>> I noticed I can now deploy to a Postgresql database but I still fail
>> on MSSQL because the RealmEntity class has not been converted to use the
>> new identity mechanism. I am sure this would have been updated before
>> alpha2 was released but I wanted to bring some attention to it just in case.
>> keycloak-user mailing list
keycloak-user mailing list