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
Copy file name to clipboardExpand all lines: doc/src/api_manual/oracledb.rst
-40Lines changed: 0 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -989,28 +989,6 @@ Each of the configuration properties is described below.
989
989
constoracledb=require('oracledb');
990
990
oracledb.events=false;
991
991
992
-
.. attribute:: oracledb.extendedMetaData
993
-
994
-
.. desupported:: 6.0
995
-
996
-
Extended metadata is now always returned
997
-
998
-
.. versionadded:: 1.10
999
-
1000
-
This property is a boolean that determines whether additional metadata is
1001
-
available for queries and for REF CURSORs returned from PL/SQL blocks.
1002
-
1003
-
The default value for ``extendedMetaData`` is *false*. With this value,
1004
-
the :ref:`result.metaData <execmetadata>` and :attr:`resultSet.metaData`
1005
-
objects only include column names.
1006
-
1007
-
If ``extendedMetaData`` is *true* then ``metaData`` will contain
1008
-
additional attributes. These are listed in :ref:`Result Object
1009
-
Properties <execmetadata>`.
1010
-
1011
-
This property may be overridden in an :ref:`execute() <executeoptions>`
1012
-
call.
1013
-
1014
992
.. attribute:: oracledb.externalAuth
1015
993
1016
994
This property is a boolean value. If this property is *true* in
@@ -2116,24 +2094,6 @@ Oracledb Methods
2116
2094
.. versionchanged:: 5.5
2117
2095
2118
2096
The ``accessToken`` property was extended to allow OAuth 2.0 token-based authentication in node-oracledb 5.5. For OAuth 2.0, the property should be a string, or a callback. For node-oracledb Thick mode, Oracle Client libraries 19.15 (or later), or 21.7 (or later) must be used. The callback usage supports both OAuth 2.0 and IAM token-based authentication.
2119
-
* - ``accessTokenCallback``
2120
-
- Object
2121
-
- NA
2122
-
- .. _createpoolpoolattrsaccesstokencallback:
2123
-
2124
-
This optional attribute is a Node.js callback function. It gets called by the connection pool if the pool needs to grow and create new connections but the current token has expired.
2125
-
2126
-
The callback function must return a JavaScript object with attributes ``token`` and ``privateKey`` for IAM. See :ref:`Connection Pool Creation with Access Tokens for IAM <iampool>`.
2127
-
2128
-
.. versionadded:: 5.4
2129
-
2130
-
It should be used with Oracle Client libraries 19.14 (or later), or 21.5 (or later).
2131
-
2132
-
.. deprecated:: 5.5
2133
-
2134
-
.. desupported:: 6.0
2135
-
2136
-
Use :ref:`accessToken <createpoolpoolattrsaccesstoken>` with a callback instead.
When a connect descriptor is specified in the ``connectString`` property as
221
+
shown in the example above, the maximum length of the ``DESCRIPTION``
222
+
parameter is *4096* bytes and its maximum nesting depth (maximum level of
223
+
sub-sections inside the DESCRIPTION section + 1) is *64*. If either limit is
224
+
exceeded, an error is raised.
225
+
220
226
Any ``DESCRIPTION``, ``CONNECT_DATA`` and ``SECURITY`` parameters of a connect
221
227
descriptor that are not recognized by node-oracledb are passed to the database
222
228
unchanged.
@@ -685,7 +691,7 @@ below.
685
691
.. versionadded:: 6.10
686
692
- Optional
687
693
* - ``njs``
688
-
- The node-oracledb specific properties. The properties that can be stored in OCI Object Storage include ``poolMin``, ``poolMax``, ``poolIncrement``, ``poolTimeout``, ``poolPingInterval``, ``poolPingTimeout``, ``stmtCacheSize``, ``prefetchRows``, and ``lobPrefetch``.
694
+
- The node-oracledb specific properties. The properties that can be stored include ``poolMin``, ``poolMax``, ``poolIncrement``, ``poolTimeout``, ``poolPingInterval``, ``poolPingTimeout``, ``stmtCacheSize``, ``prefetchRows``, and ``lobPrefetch``.
689
695
- Optional
690
696
691
697
**Precedence of Properties**
@@ -755,7 +761,7 @@ Provider is:
755
761
"user": "scott",
756
762
"password": {
757
763
"type": "base64",
758
-
"value": "dGlnZXI="
764
+
"value": "***xyz"
759
765
}
760
766
"njs": {
761
767
"stmtCacheSize": 30,
@@ -827,7 +833,7 @@ Multiple alias names can be defined in a JSON file as shown below:
827
833
"user": "scott",
828
834
"password": {
829
835
"type": "base64",
830
-
"value": "dGlnZXI="
836
+
"value": "***xyz"
831
837
}
832
838
}
833
839
}
@@ -1367,7 +1373,7 @@ An example of a JSON file that can be used with AWS S3 Configuration Provider is
1367
1373
"user": "scott",
1368
1374
"password": {
1369
1375
"type": "base64",
1370
-
"value": "dGlnZXI="
1376
+
"value": "***xyz"
1371
1377
},
1372
1378
"njs": {
1373
1379
"stmtCacheSize": 30,
@@ -2053,6 +2059,8 @@ connection is shown below:
2053
2059
user:"hr",
2054
2060
password: mypw, // contains the hr schema password
2055
2061
connectString:"mydbmachine.example.com/orclpdb1",
2062
+
walletLocation:"/opt/OracleCloud/MYDB", // location of pem file
0 commit comments