Support #2383
write an SQL script to verify all UDFs for built-in functions work once p2jpl.jar is installed in a database
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
History
#1 Updated by Eric Faulhaber over 9 years ago
The p2jpl.jar contains a subset of the full P2J runtime classes. We recently found (in #2362) that one of the Progress built-in functions implemented as a PostgreSQL UDF (entry) does not work, because of a missing dependency in p2jpl.jar file.
We need an SQL script for regression testing, which invokes each of the UDFs to verify they do not have similar problems. We do not need to use each signature variant of every API, but we do need to invoke at least one of each UDF which invokes a specific entry point in the P2J runtime, in order to flush out any missing dependencies.
The script should be named verify_udf_dependencies.sql, and should reside in the pl subdirectory of the P2J project.