Support Article
Obj-Browse is throwing PSQLException
SA-51459
Summary
In Pega 7.3, PSQLException occurs when retrieving data using Obj-Browse and PostgreSQL database. However, the same code works in Oracle and Pega 7.1.8.
Error Messages
org.postgresql.util.PSQLException: ERROR: operator does not exist: numeric = character varying
Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.
Position: 377
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169) ~[postgresql-42.1.1.jar:42.1.1]
at org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:158) ~[postgresql-42.1.1.jar:42.1.1]
Steps to Reproduce
Run the activity that calls an Obj-Browse of a table.
Root Cause
An issue in the custom application code or rules. In Pega, a property is defined as a Text, however, the database column is Numeric.
Oracle queries a number column like it is a String. PostgreSQL does not perform this implicit conversion and hence generates errors.
Resolution
Perform either of the following local-changes:
- Change the property within Pega to Integer.
- Change the column within the database to varchar.
Published April 12, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.