@@ -754,7 +754,7 @@ fetches](#fetchingrows), during ResultSet [`getRow()`](#getrow) calls,
754
754
and for [ ` queryStream() ` ] ( #querystream ) . It is not used for
755
755
[ ` getRows() ` ] ( #getrows ) .
756
756
757
- Increasing this value reduces the number of round trips to the
757
+ Increasing this value reduces the number of round- trips to the
758
758
database but increases memory usage for each data fetch. For queries
759
759
that return a large number of rows, higher values of ` fetchArraySize `
760
760
may give better performance. For queries that only return a few rows,
@@ -2493,7 +2493,7 @@ Pinging doesn't replace error checking during statement execution,
2493
2493
since network or database failure may occur in the time between
2494
2494
` ping() ` and ` execute() ` calls.
2495
2495
2496
- Pinging requires a ' round trip' to the database so unnecessary ping
2496
+ Pinging requires a round- trip to the database so unnecessary ping
2497
2497
calls should be avoided.
2498
2498
2499
2499
If ` ping() ` returns an error, the application should close the
@@ -4529,7 +4529,7 @@ connection.execute(
4529
4529
);
4530
4530
` ` `
4531
4531
4532
- To do this without requiring the overhead of a ' round trip' to execute
4532
+ To do this without requiring the overhead of a round- trip to execute
4533
4533
the ` ALTER ` statement, you could use a PL/SQL trigger:
4534
4534
4535
4535
` ` ` sql
@@ -6947,7 +6947,7 @@ to identify and resolve unnecessary database resource usage, or
6947
6947
improper access.
6948
6948
6949
6949
The attributes are set on a [connection](#propdbconclass) object and
6950
- sent to the database on the next ' round-trip' from node-oracledb, for
6950
+ sent to the database on the next round-trip from node-oracledb, for
6951
6951
example, with ` execute ()` :
6952
6952
6953
6953
` ` ` javascript
0 commit comments