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
+18-9Lines changed: 18 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3110,7 +3110,7 @@ The `message` parameter in the notification callback is an object containing the
3110
3110
-`rowid` - a string containing the ROWID of the row that was affected
3111
3111
-`txId` - a buffer containing the identifier of the transaction which spawned the notification.
3112
3112
-`type` - the type of notification sent. This will be the value of one of the following constants:
3113
-
-[`oracledb.SUBSCR_EVENT_TYPE_AQ`](#oracledbconstantssubscription) - One or more Advanced Queuing messages are available for to be dequeued (Note AQ enqueue and dequeue methods are not supported)
3113
+
-[`oracledb.SUBSCR_EVENT_TYPE_AQ`](#oracledbconstantssubscription) - One or more Advanced Queuing messages are available to be dequeued (Note AQ enqueue and dequeue methods are not supported)
3114
3114
-[`oracledb.SUBSCR_EVENT_TYPE_DEREG`](#oracledbconstantssubscription) - the subscription has been closed or the timeout value has been reached.
3115
3115
-[`oracledb.SUBSCR_EVENT_TYPE_OBJ_CHANGE`](#oracledbconstantssubscription) - object-level notications are being used (Database Change Notification).
3116
3116
-[`oracledb.SUBSCR_EVENT_TYPE_QUERY_CHANGE`](#oracledbconstantssubscription) - query-level notifications are being used (Continuous Query Notification).
@@ -7957,10 +7957,11 @@ The connection must be created with [`events`](#propdbevents) mode
7957
7957
7958
7958
The database must be able to connect to the node-oracledb machine for
7959
7959
notifications to be received. Typically this means that the machine
7960
-
running node-oracledb needs a fixed IP address. If there is any
7961
-
problem sending a notification, then the callback method will not be
7962
-
invoked. The configuration options can include an
7963
-
[`ipAddress`](#consubscribeoptipaddress) and
7960
+
running node-oracledb needs a fixed IP address. Note
7961
+
`connection.subscribe()` does not verify that this reverse connection
7962
+
is possible. If there is any problem sending a notification, then the
7963
+
callback method will not be invoked. The configuration options can
7964
+
include an [`ipAddress`](#consubscribeoptipaddress) and
7964
7965
[`port`](#consubscribeoptport) on which to listen for notifications,
0 commit comments