Error while trying to use hex160 as primary key or with unique flag

[0xMimir]

When trying to create following table:

create table example(
    id uuid primary key default uuid_generate_v4(),
    account hex160 not null unique,
    username varchar(50) not null unique
)

Or

create table example(
    id hex160 primary key,
    username varchar(50) not null unique
)

I get following error

ERROR: data type hex160 has no default operator class for access method "btree"

[Yen]

I believe the issue is that making a primary key or a unique constraint on a field results in this case a btree index being created, and this isn't possible for the new data types. This is only the theory from a quick look at the postgres docs. As it is possible to define these operators, you may be able to do this with user defined functions if it's a hard requirement for you. If not, I will look into this in the new year and hopefully it's just a few extra functions that need to be defined. For the time being, if acceptable, avoid using the data types in constraints for now and they can be migrated to in a future version.