In PostgreSQL, database objects name (column name, table name, etc) are handled in lower case. This is by their design, and it's not up to Pega. Let's say, we create a class and properties with letters that starts with upper case (This is a Java/Pega standard practice) as below.
Pega Platform automatically creates a table and columns as below - all with lower case letters.
This may sometimes cause an issue. For example, if you use Obj-Browse method in an activity to retrieve data from this table, it loads them all with lower case letters - hence you won't be able to reference the data by Property name.
In order to avoid this issue, you'll need to map them in the class form as below.
This issue has been a while but is there any enhancement yet? It doesn't happen in Oracle.
FYI, below link talks about the same issue but there is not applicable solution provided.
If you map an existing table outside of Pega database using "External Database Class Mapping" tool, system will create classes and properties all by lower case from the beginning. So there is no need to update External mapping in a class form in that case. I am talking about when you create properties with upper case in an internal database using Data type - system doesn't update External mapping by itself.
Posted: 1 year ago
Posted: 13 May 2020 21:54 EDT
Mudit Manchanda (mancm1)
Associate Technical Solutions Engineer