+1 on UUIDs; we do same on UPS<br><br>On Friday, February 7, 2014, Stian Thorgersen &lt;<a href="mailto:stian@redhat.com">stian@redhat.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I propose we use java.util.UUID to IDs generated by DB (JPA @GeneratedValue). Reasoning behind this is:</blockquote><div><br></div>W/ the hibernate specific annotations? <br><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
* IDs are the same independent of store used (JPA, Mongo, PicketLink, LDAP, etc)<br>
* Easy to support many RDBMS (some support sequence and/or identity, so it seems the recommended approach when you don&#39;t know what the db will be is table)<br>
* IDs can be generated without a &quot;central&quot; db<br>
<br>
Also, we&#39;d like to be able to export all data to a json then import into any store. We then need to make sure there&#39;s no conflicts in IDs. For example you first use KC with H2, then export all data, import into MySQL, then export all data, import into Mongo. I can see that causing some issues with IDs generated by DB.<br>

<br>
This is related to DB issues (Mysql, PostgreSQL not working), Mongo store impl as well as move to using user id instead of username as the reference for a user.<span></span> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;keycloak-dev@lists.jboss.org&#39;)">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</blockquote><br><br>-- <br>Sent from Gmail Mobile<br>