-
Type:
Improvement
-
Resolution: Invalid
-
Priority:
Minor
-
None
-
Affects Version/s: 5.13.1
-
Component/s: provisioning
-
None
While setting up a new SQL Provisioner (to Postgres), I thought I would take advantage of the numeric idIndex properties of Groups and Entities, defining my provisioning-target tables with BIGINT columns. When I tried to use idIndex properties for my two primary-key columns, the provisioner got errors with incompatibilities between TEXT and BIGINT types. I certainly wish Postgres hadn't removed the implicit cast from TEXT to numbers, but it did. I thought about creating a CAST, but I gave into all the FUD about implicit casts and did try it.
It looks like the provisioner is doing all it's work with strings. I tried to circumvent this by using a jexl snippet of provisionedGroup.getIdIndex(), but this didn't seem to work.
I also see that one of Groups or Entities has both idIndex & idIndexString and the other just idIndex... so it looks like there's some thoughts already in this area.
Anyway, I just wanted to highlight that this didn't work for me; perhaps I messed something up. Nonetheless, I've reverted to TEXT columns and indexes and am happy enough.