[dev] [commits] Horde branch master updated. c1f241be16aa88a278d0e51fc7baa78e39008cca

[Chuck Hagenbuch]

Any reason this isn't just an option when creating uuids?

Michael M Slusarz <slusarz at horde.org> wrote:

>Quoting Chuck Hagenbuch <chuck at horde.org>:
>
>> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>>
>>> It seems un-friendly to require a schema simply because we've  
>>> changed our id generation for these fields. We can truncate the id  
>>> when it's generated in the affected apps, but I'm unsure how that  
>>> affects the uniqueness of the id. Or we could go back to the old  
>>> way of generating the ids in these cases. Not sure why a UUID is  
>>> needed in some of these cases - like for kronolith's event_id  
>>> field, for instance.
>>
>> I think we should go ahead and increase the field length, or we  
>> should go back to auto-increment ids. We don't need UUIDs here at  
>> all - I think we thought at one point that we could combine the id  
>> with the uid, but we can't, so...
>
>Alternatively, we could use Horde_Support_Randomid instead (which I  
>just committed) - which produces more compact IDs than the UUIDs since  
>it packs the data into base-36 instead of base-16 (and doesn't have  
>any extraneous dashes).
>
>michael
>
>-- 
>___________________________________
>Michael Slusarz [slusarz at horde.org]
>
>
>-- 
>Horde developers mailing list - Join the hunt: http://horde.org/bounties/
>Frequently Asked Questions: http://horde.org/faq/
>To unsubscribe, mail: dev-unsubscribe at lists.horde.org