[TYPO3-core] Universally/Globally Unique IDentifier in core in 6.0?

[JoH asenau]

>> the next thing I wanted to implement in EXT:identity is relation
>> support. We will keep the sequencial id's but just as technical
>> identifier. You can't change that, as every extension and nearly every
>> core module expects the uid to be a integer. If it's not the module
>> thinks it's a new record.
>
> I was actually thinking about using the UUID as primary identifier in
> the core and keeping the currently used sequential uid during the
> deprecation phase to keep old code working.
>
> This will of course have quite an impact on all core modules. We need to
> add new TS properties for the UUID and deprecate the current properties,
> etc.
>
> What do you think?

IMHO there is a huge difference between just having uid support in TYPO3 
and switching the whole normalization system from INT uid to NON INT uuid.

Especially performance will be a problem, since most of the TYPO3 
installations are based on MySQL which does not perform too well with 
non-numerical-indexing.

IMHO there is no need to replace the current behaviour completely.
Instead we should provide UUID support as additional feature that can be 
enabled/used on demand. Especially export and reimport of records and 
cross domain sharing of content will be uses cases for that, but as long 
as there is no need for these special features the rest of the TYPO3 
world could stay with the usual normalization and have less problems.

Just my 2 cents.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com