You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client-libraries required for SODA production use: 18.5 and above.
Oracle Database: 18 and above.
Known issues affecting SODA node.js are:
(1) Bug 28533043 - this is an issue at OCI level affecting performance of "finds" that return multiple documents. Due to lack of reliance on OCI array fetch, which allows fetching multiple documents in one round-trip, fetching each document requires a round-trip to the database. Status: fixed, now getting backported to 18.x and 19.x DBRU.
(2) Bug 29607136 - this is an RDBMS-side bug is in index specification processing: when multiple varchar2 fields are indexed, an error is produced (instead of a successful index create). The error is in automatic computation of maxLength field of the index spec. Status: fixed, now getting backported to 18.x and 19.x DBRU. There's an easy workaround for this bug, which is to specify the maxLength field explicitly for each varchar2 field of the index spec.
(3) Bug 29523511 - this is an issue at OCI level. It's a memory leak when QBE is used and NLS_LANG specified client character set is other than AL32UTF8. Status: fixed, now getting backported to 19.x DBRU.
Enhancement Requests
Case insensitive sorting. Requested for node.js driver, but the same issue applies to ODPI-C as well. See node.js issue 1099
The text was updated successfully, but these errors were encountered:
This is to track known SODA issues.
Client-libraries required for SODA production use: 18.5 and above.
Oracle Database: 18 and above.
Known issues affecting SODA node.js are:
(1) Bug 28533043 - this is an issue at OCI level affecting performance of "finds" that return multiple documents. Due to lack of reliance on OCI array fetch, which allows fetching multiple documents in one round-trip, fetching each document requires a round-trip to the database. Status: fixed, now getting backported to 18.x and 19.x DBRU.
(2) Bug 29607136 - this is an RDBMS-side bug is in index specification processing: when multiple varchar2 fields are indexed, an error is produced (instead of a successful index create). The error is in automatic computation of maxLength field of the index spec. Status: fixed, now getting backported to 18.x and 19.x DBRU. There's an easy workaround for this bug, which is to specify the maxLength field explicitly for each varchar2 field of the index spec.
(3) Bug 29523511 - this is an issue at OCI level. It's a memory leak when QBE is used and NLS_LANG specified client character set is other than AL32UTF8. Status: fixed, now getting backported to 19.x DBRU.
Enhancement Requests
The text was updated successfully, but these errors were encountered: