Question
Amazon
IN
Last activity: 4 Aug 2018 1:06 EDT
Obj Methods return properties in lower case - PostgreSQL
When PEGA is used with Oracle-RDS, all Obj methods return UPPERCASE properties, but when used with PostgreSQL it returns lowercase properties. This is causing an issue when migrating applications across Databases. Is there a DSS or configuration to ensure SQL generated by PEGA when interacting with DB can be defaulted to UPPER / lower case?
Pegasystems Inc.
IN
Hi,
You can try writing the query by overriding the column name as follows:
select Name as "name" from demo.
with this you will be able to standardized the column names regardless of any database.
JPMorgan Chase & Company
US
Hi,
Could you please let us know what is the issue you are facing while migrating, I hope the databases accept queries in case insensitive.
Amazon
IN
Hi Sudhakar
It seems postgres defaults to lowercase and Oracle to UPPERCASE for all queries.
I am specifically looking for a scenario of Obj-Browse where i want to fetch all columns of a table and have not added the property names individually in the select clause of the method.
If I select the properties individually the mapping is perfect.
But if I do not, the query looks something like - select column_1 as "column_1".... when connected to Postgres, whereas in Oracle this would be - SELECT COLUMN_1 AS "COLUMN_1".....
Pegasystems Inc.
US
Nordea
SE
Could you please elaborate where should we define this. From Pega we have external mapping of properties which is already there.No issue with Obj-Browse but at the time of obj-open/Obj-Open_by Handle we are facing this upper case columns issue.