@@ -1831,6 +1831,8 @@ The default value is 500.
1831
1831
1832
1832
This property may be overridden when [creating a connection pool](#createpool).
1833
1833
1834
+ This property was added in node-oracledb 5.0.
1835
+
1834
1836
##### Example
1835
1837
1836
1838
```javascript
@@ -2243,6 +2245,8 @@ The default value is 500.
2243
2245
This optional property overrides the
2244
2246
[`oracledb.queueMax`](#propdbqueuemax) property.
2245
2247
2248
+ This property was added in node-oracledb 5.0.
2249
+
2246
2250
###### <a name="createpoolpoolattrsqueuerequests"></a> 3.3.1.1.15 `queueRequests`
2247
2251
2248
2252
This property was removed in node-oracledb 3.0 and queuing was always enabled.
@@ -5562,6 +5566,8 @@ The maximum number of pending `pool.getConnection()` calls that can be
5562
5566
5563
5567
See [`oracledb.queueMax`](#propdbqueuemax).
5564
5568
5569
+ This property was added in node-oracledb 5.0.
5570
+
5565
5571
#### <a name="proppoolqueuerequests"></a> 8.1.10 `pool.queueRequests`
5566
5572
5567
5573
This property was removed in node-oracledb 3.0. See [Connection Pool
@@ -16213,11 +16219,6 @@ When upgrading from node-oracledb version 4.0 to version 4.1:
16213
16219
16214
16220
- Review the [CHANGELOG][83] and take advantage of new features.
16215
16221
16216
- Choose a sensible value for the new *Pool* [`queueMax`](#propdbqueuemax)
16217
- attribute, so that applications get the new error only under abnormal
16218
- connection load. To allow all pooled connection requests to be queued (the
16219
- previous behavior), set it to 0.
16220
-
16221
16222
- Review your application use of node-oracledb error messages since some have changed.
16222
16223
16223
16224
- Note that the default for [`oracledb.events`](#propdbevents) has reverted to
@@ -16244,6 +16245,11 @@ When upgrading from node-oracledb version 4.0 to version 4.1:
16244
16245
Node-oracledb](#initnodeoracledb), particularly around how node-oracledb can
16245
16246
locate Oracle Client libraries.
16246
16247
16248
+ - Choose a sensible value for the new *Pool* [`queueMax`](#propdbqueuemax)
16249
+ attribute, so that applications get the new error only under abnormal
16250
+ connection load. To allow all pooled connection requests to be queued (the
16251
+ previous behavior), set it to -1.
16252
+
16247
16253
- Take advantage of the new [`prefetchRows`](#propexecprefetchrows) attribute to
16248
16254
re-tune SQL queries.
16249
16255
0 commit comments