Confusion – cursor.read(...) Query(cursor).read(...)

[jglodek]

I think this might have changed somewhere along the road.

I definitely get when I do query(cursor).read(...),

(node:17795) UnhandledPromiseRejectionWarning: TypeError: cursor.read is not a function
    at postgres.connect.then (/root/scraper/interpret_scaped_data.js:69:10)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

And

query(cursor).then((cursor) => {cursor.read(...)}) doesn't work the promise never gets there.

[netlify]

Hey! A preview of the changes is deployed on netlify to take a look at! :)

Built with commit a82affb

https://deploy-preview-51--hopeful-clarke-f36d36.netlify.com

[brianc]

Good catch - sorry about that! That's actually kinda weird that it returns a promise when you pass a cursor in.

https://github.com/brianc/node-postgres/blob/master/lib/client.js#L466

What version of pg & pg-cursor are you using, out of curiosity?

[charmander]

This isn’t how it’s supposed to work. Are you sure you’re using client.query() and not pool.query()?