I changed it as I couldn't get the composite ids to work. Did I break something?
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Friday, 18 July, 2014 5:26:32 PM
Subject: Re: [keycloak-dev] more db schema changes
Nevermind. Stian changed it already. Not sure why now...
On 7/18/2014 12:03 PM, Bill Burke wrote:
> Ugh. Might be the double @ManyToOne hack I had to do for auth link.
>
> On 7/18/2014 11:51 AM, Marek Posolda wrote:
>> Hi,
>>
>> just wanted to point that all recent DB changes seem to break databases
>> (or at least MySQL). Actually when running testsuite with MySQL, then at
>> the end of some tests during Hibernate schema cleanup, it hangs. Just
>> figured out that it's this SQL command which causes hang of MySQL: alter
>> table AUTHENTICATION_LINK drop foreign key FK582E5612EF007A6;
>>
>> Actually not sure if it's related to compound primary key of
>> AuthenticationLinkEntity or foreign key with UserEntity... Will look at
>> it more on Monday, just wanted to point that databases doesn't work ATM.
>>
>> Marek
>>
>> On 17.7.2014 22:36, Bill Burke wrote:
>>> * created @NamedQuery for every creatQuery we have
>>> * Use @Column, @JoinColumn, and @JoinTable, and @Table everywhere.
>>> names are uppercase with "_". At least 10+ years ago, this was
the
>>> standard naming convention.
>>> * CredentialEntity now has a generated String ID. We will want to have
>>> multiple TOTP entries in the future.
>>>
>>> Bill
>>>
>>
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev