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
While the neon() function (HTTP) doesn't support real transactions, it does support so called "non-interactive transactions" through a transaction() function.
See docs here
Do you think it would possible to support it?
As a workaround, you could add an option to pass an existing neon query object to the dialect. So the user could call neon(), pass the result to the dialect constructor, and still have access to transaction().