[FLOW3-general] uniq uid

Sam Duff skduff at gmail.com
Thu Aug 11 00:35:22 CEST 2011


To understand why UUIDs are used you really need to understand Domain Driven
Design and why Aggregates and Entities need a globally unique ID, not just a
unique ID for a specific database table.

http://en.wikipedia.org/wiki/Domain-driven_design

Kind regards,

Sam Duff


On Thu, Aug 11, 2011 at 2:15 AM, Dawid Pacholczyk <dpacholczyk at gmail.com>wrote:

> Hi
>
> [quote]
> In this context the word unique should be taken to mean "practically
> unique" rather than "guaranteed unique"
> [/quote]
>
> Now I rly don`t understand why normal int wasn`t used as a primary key.
> Beside I can`t sort with this key.
>
> For example when I have integer uid i can always use
>
> select * from table order by uid desc
>
> Now it`s impossible. Can some of the authors explain what were your
> motivations ?
>
> Best regards,
> Dawid Pacholczyk
>
> p.s. Don`t get me wrong. FLOW3 is great but I see only disadvantages in
> this solution
>
> W dniu 2011-08-10 10:15, Christian Jul Jensen pisze:
>
>> Hi David
>>
>> Dawid Pacholczyk wrote:
>>
>>> I guest this is like UID in TYPO3. I want to ask why it`s varchar with
>>> long strings and not standard auto incremented integer ?
>>>
>>
>> FLOW3 uses UUIDs as ids, they are not integers, see
>> http://en.wikipedia.org/wiki/**Universally_unique_identifier<http://en.wikipedia.org/wiki/Universally_unique_identifier>
>>
>> I am not sure exactly which uuid scheme is used.
>>
>>
> ______________________________**_________________
> FLOW3-general mailing list
> FLOW3-general at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/flow3-**general<http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general>
>


More information about the FLOW3-general mailing list