From 2d7c6b0fad5f0d024ef9eb000289f1bf64655611 Mon Sep 17 00:00:00 2001
From: Ted Monoceros <Ted.Monoceros@directsupply.com>
Date: Fri, 6 Sep 2024 12:00:48 -0500
Subject: [PATCH] Clarify timing requirements of streaming events in README

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index c6dc80e3..3a404992 100644
--- a/README.md
+++ b/README.md
@@ -351,7 +351,7 @@ sql.on('error', err => {
 
 ### Streaming
 
-If you plan to work with large amount of rows, you should always use streaming. Once you enable this, you must listen for events to receive data.
+If you plan to work with large amount of rows, you should always use streaming. Once you enable this, you must listen for events to receive data. Events must be attached before the query completes, but can be attached while in-flight.
 
 ```javascript
 const sql = require('mssql')
@@ -361,7 +361,6 @@ sql.connect(config, err => {
 
     const request = new sql.Request()
     request.stream = true // You can set streaming differently for each request
-    request.query('select * from verylargetable') // or request.execute(procedure)
 
     request.on('recordset', columns => {
         // Emitted once for each recordset in a query
@@ -383,6 +382,8 @@ sql.connect(config, err => {
     request.on('done', result => {
         // Always emitted as the last one
     })
+    
+    request.query('select * from verylargetable') // or request.execute(procedure)
 })
 
 sql.on('error', err => {