This issue is not reproducible in the latest release of ArcGIS Pro.
It is unclear which change produces a fix, but it will work fine with any version from ArcGIS Pro 3.3 and later.
If this issue persists, please provide the enterprise database provider and the version used.