So in trying to explore this issue more, I put together another branch on the [ Ecto ULID Sandbox ] repo that showcases the same issue being present when trying to use a similar Postgrex Type Extension as the primary_key.
The other extension is the [ Cube Ecto ] extension that adds support for cube data type through postgres.
branch_name: ecto_cube_primary_id
The branch showcases that using the cube field as the primary_key identifier (an absurd scenario, of course; that data type is not intended for that use case), but it showcases the issue happening there too. Currently my best guess would be that having a custom Postgrex.Ext being the primary key is likely causing this issue somehow.
