Johann,

EOF only support NSData, String, number and Date as primary key. Also, 
databases usually does not have a native uuid type because it is in fact only a 
16 bytes data value.

Samuel

> Le 22 mars 2016 à 10:13, Johann Werner <[email protected]> a écrit :
> 
> Hi Samuel,
> 
> what about using the UUID class [1]?
> 
> jw
> 
> 
> [1] https://docs.oracle.com/javase/8/docs/api/java/util/UUID.html
> 
> 
>> Am 22.03.2016 um 15:03 schrieb Samuel Pelletier <[email protected]>:
>> 
>> Hi,
>> 
>> I'm working on adding uuid support as primary key with a prototype and 
>> ERRest support. Actually, my implementation uses a 16 bytes NSData as the 
>> adaptor value type. Before going too far in this, I would like to validate 
>> my choices...
>> 
>> I see 2 options:
>> 
>> 1- A 16 bytes NSData
>> 
>>      Pro: It seems the most efficient and adapted data type.
>>      Cons: Hard to read and type in SQL queries. GlobalIds are cryptic.
>> 
>> 2- A 32 char hex string (or a 36 one if pretty printed with the dashes).
>> 
>>      Pro: Easier to read, especially with the dashes.
>>      Cons: Uses more spaces, maybe less fast. Seems a bit awkward to deal 
>> with hex strings.
>> 
>> 
>> For the ERRest part, I managed to format the uuid in a primary key by 
>> detecting if it is a 16 bytes NSData in the formatted hex representation. I 
>> also found a way to get objects using the hex representation.
>> 
>> Any though on this ? Something I missed ?
>> 
>> Finally, is a presentation on using uuid for primary key in next WOWODC 
>> would be a good topic ?
>> 
>> Samuel
> 


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to