> The dashless format is neither standards compliant nor compatible with
> other databases that have uuid functions (notably MS SQL Server and
> MySQL), nor with microsoft tools where they're used frequently.
> (ignoring the {} wrapping stuff which is trivial).
>
> If we add a UUID type to core, I think that a vast majority of the
> people who are going to want to use it out there will be expecting the
> standard format with dashes. And asking them to put a formatting
> function into every query is beyond horrific.
>
> If we want a general raw hex type then let's call it something else,
> because calling it UUID will just confuse people. Everyone else follows
> the standard on this; we should too.
Agreed to all above. The formatting issues are all handled in the patch.
Regards,
Gevik
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
