POINTER fields are inconsistent, and cause problems with some clients
As reported by an end user, it seems that there is a bug due to the inconsistent data types for POINTERS in the DDL mapper:
Pointers produce "INTEGER", as in
`PATIENT` INTEGER GLOBAL "^BPST(keys(""BPS_TRANSACTION_ID""),0)" PIECE 6
But the definition of the field is:
`PATIENT_ID` NUMERIC PRIMARY KEY START 0 ENDPOINT '$CHAR(0)'
Pointers needs to be NUMERIC
as well.
This seems to be a regression in commit a52d81ed.