Char 36 primary key's impact on performance

[frozendry]

Hi Everyone,

Anyone can help me with this?

Avoiding key collisions would incur a little extra database overhead in terms of disk space and performance.
How can I justify that using char 36 ID following the Sugar Default than using Int as primary?

[rafael.q.g@hotmail.com]

I don't know exactly what reason made sugar uses 36 chars as key instead of a integer values (with auto increment as example).
But some behaviors are:
- Each module has a single key prefix, and it makes each key unique in entire db, not just on that table.
- It also permits sugar works with Flex related fields, that based in a record key is possible to look in each module/table these records come in.

[frozendry]

Hi,

May I request test results files or documents showing performance statistics with the current sugarcrm setup (char 36 ID as primary key)

Thanks.