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/api.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1630,9 +1630,9 @@ If a bind value is an object it may have the following properties:
1630
1630
Bind Property | Description
1631
1631
---------------|------------
1632
1632
`dir` | The direction of the bind. One of the [Oracledb Constants](#oracledbconstantsbinddir)`BIND_IN`, `BIND_INOUT`, or `BIND_OUT`.
1633
-
`maxArraySize` | The number of array elements to be allocated for a PL/SQL Collection `INDEX OF` associative array OUT or IN OUT array bind variable.
1634
-
`maxSize` | The maximum number of bytes that an OUT or IN OUT bind variable of type `STRING` or `BUFFER` can use to get data. The default value is 200. The maximum limit depends on the database type.
1635
-
`type` | The datatype to be bound. One of the [Oracledb Constants](#oracledbconstantsbinddir)`BLOB`, `BUFFER`, `CLOB`, `CURSOR`, `DATE`, `NUMBER`, or `STRING`.
1633
+
`maxArraySize` | The number of array elements to be allocated for a PL/SQL Collection `INDEX OF` associative array OUT or IN OUT array bind variable. For IN binds, the value of `maxArraySize` is ignored.
1634
+
`maxSize` | The maximum number of bytes that an OUT or IN OUT bind variable of type `STRING` or `BUFFER` can use to get data. The default value is 200. The maximum limit depends on the database type, see below. When binding IN OUT, then `maxSize` refers to the size of the returned value: the input value can be smaller or bigger. For IN binds, `maxSize` is ignored.
1635
+
`type` | The datatype to be bound. One of the [Oracledb Constants](#oracledbconstantsbinddir)`BLOB`, `BUFFER`, `CLOB`, `CURSOR`, `DATE`, `NUMBER`, or `STRING`. With IN OUT binds the type can be explicitly set with `type` or it will default to the type of the input data value. With OUT binds, the type defaults to `STRING` whenever `type` is not specified.
1636
1636
`val` | The input value or variable to be used for an IN or IN OUT bind variable.
1637
1637
1638
1638
The limit for `maxSize` when binding as a `BUFFER` type is 2000 bytes,
@@ -1644,13 +1644,6 @@ When binding Oracle LOBs, as `STRING` or `BUFFER`, the value of
1644
1644
`maxSize` can be much larger, see the limits
1645
1645
in [LOB Bind Parameters](#lobbinds).
1646
1646
1647
-
When binding IN OUT, then `maxSize` refers to the size of the returned
1648
-
value. The input value can be smaller or bigger.
1649
-
1650
-
With OUT binds, where the type cannot be inferred by node-oracledb
1651
-
because there is no input data value, the type defaults to `STRING`
1652
-
whenever `type` is not specified.
1653
-
1654
1647
Note `CURSOR` bind variables can be used only for PL/SQL OUT binds.
0 commit comments