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
After this commit, pg.Result.fields will be an array only after pg.Result.addFields() is called.
However, pg.Result.addFields() is called only in the callback of RowDescription event, which is dispatched by pg in response to a SELECT, FETCH, etc query. If I send sqls like create SCHEMA hello, the pg.Result.fields will remain undefined. This behavior is different from the doc:
Every result will have a fields array.
Please heve a look. Thanks.
The text was updated successfully, but these errors were encountered:
ahh dang yeah I need to fix that, sorry about the hassle there. I cut the end of my finger off on NYE 🤕 and juuust about healed up but haven't realy been able to type effectively up until yesterday...I'll get a change for backwards compatibility (+ a test for this) released ASAP (1-2 days 🤞 )
After this commit,
pg.Result.fields
will be an array only afterpg.Result.addFields()
is called.However,
pg.Result.addFields()
is called only in the callback ofRowDescription
event, which is dispatched by pg in response to a SELECT, FETCH, etc query. If I send sqls likecreate SCHEMA hello
, thepg.Result.fields
will remain undefined. This behavior is different from the doc:Please heve a look. Thanks.
The text was updated successfully, but these errors were encountered: