We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql.notify
Basically this:
sql.notify('test'); // works sql.begin(sql => { sql.notify('test') // throws Uncaught TypeError: sql.notify is not a function }}
Is that expected behavior? I am under the impression that NOTIFY should work in a transaction context as per the docs.
NOTIFY
As a workaround I think sql.unsafe works.
sql.unsafe
Coincidentally, I think the same applies to sql.listen, although I only have a use case for .notifying in transactions.
sql.listen
.notify
PS: Thanks for this library! ❤️
The text was updated successfully, but these errors were encountered:
Oh that's a good catch. Thank you!
sql.listen won't work cause it's using a dedicated connection for that, but sql.notify should work with the transaction instance as well.
And than you for the kind words ;)
Sorry, something went wrong.
0dac913
Support notify for transactions and reserved connections as well. fixes
33b6906
porsager#611
No branches or pull requests
Basically this:
Is that expected behavior? I am under the impression that
NOTIFY
should work in a transaction context as per the docs.As a workaround I think
sql.unsafe
works.Coincidentally, I think the same applies to
sql.listen
, although I only have a use case for.notify
ing in transactions.PS: Thanks for this library! ❤️
The text was updated successfully, but these errors were encountered: