@@ -3714,7 +3714,7 @@ end-of-fetch at the same time.
37143714The value of ` prefetchRows` size is ignored when *not* using a
37153715` ResultSet` .
37163716
3717- Prefetching from REF CURSORS requires Oracle Database 11gR2 or
3717+ Prefetching from REF CURSORS requires Oracle Database 11.2 or
37183718greater.
37193719
37203720Prefetching can be disabled by setting ` prefetchRows` to 0.
@@ -4540,7 +4540,8 @@ statement text is different and would be less efficient.
45404540
45414541IN binds are values passed into the database. OUT binds are used to
45424542retrieve data. IN OUT binds are passed in, and may return a different
4543- value after the statement executes.
4543+ value after the statement executes. IN OUT binds can be used for
4544+ PL/SQL calls, but not for SQL.
45444545
45454546OUT bind parameters for ` RETURNING INTO ` clauses will always return an
45464547array of values. See [DML RETURNING Bind Parameters](#dmlreturn).
@@ -4813,7 +4814,7 @@ CURSOR is set to NULL or is not set in the PL/SQL procedure then the
48134814returned ` ResultSet` is invalid and methods like ` getRows ()` will
48144815return an error when invoked.
48154816
4816- When using Oracle Database 11gR2 or greater, then
4817+ When using Oracle Database 11.2 or greater, then
48174818[` prefetchRows` ](#propdbprefetchrows) can be used to tune the
48184819performance of fetching REF CURSORS.
48194820
@@ -4968,28 +4969,32 @@ size used for these binds in the OUT direction is 200, so set
49684969See [Working with CLOB and BLOB Data](#lobhandling) for examples and
49694970more information on binding and working with LOBs.
49704971
4971- #### Maximum Limits (Bytes) for Binding LOBs to Strings and Buffers
4972+ #### Theoretical Limits (Bytes) for Binding LOBs to Strings and Buffers
49724973
4973- DB Type | Bind Type | Direction | Oracle Client 12c Limit<sup>*</sup> | Oracle Client 11g Limit<sup>*</sup>
4974+ DB Type | Bind Type | Direction | Oracle Client 12c Limit<sup>*</sup> | Oracle Client 11.2 Limit<sup>*</sup>
49744975--------|-----------------|-------------|-------------------------|------------------------
4975- CLOB | oracledb.STRING |BIND_IN | 2 GB | 64 KB
4976+ CLOB | oracledb.STRING |BIND_IN | 1 GB | 64 KB
49764977CLOB | oracledb.STRING |BIND_OUT | 1 GB | 64 KB
49774978CLOB | oracledb.STRING |BIND_INOUT | 32 KB | 32 KB
4978- BLOB | oracledb.BUFFER |BIND_IN | 2 GB | 64 KB
4979- BLOB | oracledb.BUFFER |BIND_OUT | 2 GB | 64 KB
4979+ BLOB | oracledb.BUFFER |BIND_IN | 1 GB | 64 KB
4980+ BLOB | oracledb.BUFFER |BIND_OUT | 1 GB | 64 KB
49804981BLOB | oracledb.BUFFER |BIND_INOUT | 32 KB | 32 KB
49814982
4982- <sup>*</sup>The largest usable data length is one byte less than the size shown.
4983-
4984- Internally, node-oracledb uses temporary LOBs when binding Strings and
4985- Buffers larger than 32 KB. Since temporary LOBs cannot be used for IN
4986- OUT binds, the data size in this case is restricted to 32 KB.
4983+ <sup>*</sup>The largest usable data length is two bytes less than the
4984+ size shown for 12c and one byte less for 11.2.
49874985
49884986In practice, the limitation on binding IN or OUT is the memory
4989- available to Node.js. You will see the error *JavaScript heap out of
4990- memory* when you try to create large Strings or Buffers. So, for most
4991- large data sizes, it is recommended to bind as ` oracledb .CLOB ` or
4992- ` oracledb .BLOB ` and use [Lob streaming](#streamsandlobs).
4987+ available to Node.js and the V8 engine. For data larger than several
4988+ megabytes, it is recommended to bind as ` oracledb .CLOB ` or
4989+ ` oracledb .BLOB ` and use [Lob streaming](#streamsandlobs). If you try
4990+ to create large Strings or Buffers in Node.js you will see errors like
4991+ *JavaScript heap out of memory*, or other space related messages.
4992+
4993+ Internally, for PL/SQL calls, node-oracledb uses temporary LOBs when
4994+ binding Strings and Buffers larger than 32 KB. Since temporary LOBs
4995+ cannot be used for IN OUT binds, the data size in this case is
4996+ restricted to 32 KB. For SQL call no temporary LOBs are used.
4997+
49934998
49944999### <a name="plsqlindexbybinds"></a> 13.6 PL/SQL Collection Associative Array (Index-by) Bind Parameters
49955000
0 commit comments