Posted: 11 May 2019 22:54 EDT Last activity: 13 May 2019 1:01 EDT
Unsupported colum date
Using prod 8.1.4 with Postgres dB. I have columns of type date. Query by storing values of the date columns in datetime propertiesand it works fine, But when saving a work object with datetime properties as exposed date columns I get unsupported column type of date errors upon commit. I’ve seen some articles implying Pega does not support date columns with Postgres the though they are a little old. Is this the case? What data type and property type should I be using for dates with Postgres?
I did used to have it a varchar 8 and that was working but was wondering if there was a universal solution, best practice. I'd have to submit a request to cloud team to change it again and see. I suppose the readonly columns such as in our external data can be a date while my work tables I make them a varchar but it would be good to follow some best practice.
This is known limitation with product as of now, we have already raised an enhancement request to Product management team for mapping a DATE column in postgres to a date property within pega and to implement it in future releases.
The work around for this is to Change the property within Pega that maps to the DATE database column to a text property.
So I changed my property to text and I still get this error upon commit after obj-save of my work object:
Database column .Enrollment.dob in database pegadata, table pegadata.pc_NS_BCBSMN_PI_Work_e4cb7 has an unknown type: JDBC Type: Date
If pega has raised an enhancement request then we should wait for the later version in which it will be resolved.As of now you can proceed with suggested work around.Thanks for sharing the information.