New base32hex 26-character unpadded format for UUID

[sergeyprokhorenko]

It is necessary to expand the wording:

3.2.2.20. uuid
A universally unique identifier.¶

• Base type: string¶
• Constraints:¶
  • The string value MUST conform to the [RFC9562] UUID format or [RFC4648] base32hex 26-character unpadded format.¶

See x4m/postgres_g@aa902bb

[clemensv]

@sergeyprokhorenko I will review

[sergeyprokhorenko]

@clemensv

The authors of RFC 9562 are currently considering including one of the UUID encodings, Base64Sort or Base52Sort, in the standard. A decision has not yet been made. Base32hex is unlikely to be included in the standard, as it is less compact.

[clemensv]

@sergeyprokhorenko should we add a type qualifier that selects the encoding?

[sergeyprokhorenko]

@clemensv

should we add a type qualifier that selects the encoding?

Yes, this is a good solution