Downloads
Product availability Matrix (PAM)
Downloads of this patch are available from the
Rocket Customer Support Portal.
Further explanation can be found
here.
Fixes
| UNI-38026 | Performance problems with the MSS, MQL and PGS connectors even when stmtcache is set to 'on'. |
| UNI-37268 | Second retrieve fails in very specific circumstances |
UNI-38026 - Performance problems with the MSS, MQL and PGS connectors even when stmtcache is set to 'on'.
Solution available in patch(es): 10.4.02-052
Description:
When the 'stmtcache' option is turned on some prepared statements are still not being cached. This means these statements need to be re-prepared every time. In addition, the way this caching was implemented had some unnecessary overhead. This overhead has been removed. As a consequence, the 'open statements' setting has lost its meaning. Uniface does not limit the number of cached statements anymore, this is now left to the database.
Environment:
+Uniface: Version 10.4.02
+Operating System: OS independent
+Database: MS SQL Server, MySQL, PostgreSQL
Workaround:
There is no workaround for this problem.
Notes:
This problem is solved. The 'open statements' setting is now obsolete, it has no function anymore.
UNI-37268 - Second retrieve fails in very specific circumstances
Solution available in patch(es): 10.4.02-052
Description:
A table has a primary key field like PK (VC40), and 3 index fields like:
INDEX1 (VC4000), INDEX2 (VC128) and INDEX3 (VC128), first retrieve the record with only (small field) PK as retrieve profile, then retrieve the record with (large field) INDEX1 as retrieve profile, the second retrieve fails.
This only happens when the driver option stmtcache is enabled (by default).
The issue can typically be seen when a small (compound) primary key is being used and when the index is based on large field(s).
When the first retrieve is done using the a larger field, the issue can not be seen.
Environment:
+Uniface Version : 10.4.02
+Operating System : All platforms
+Database : PostgreSQL, MS SQL Server, MySQL, DB2, SQLite
Workaround:
Disable statement cache
Notes:
This problem has been fixed.