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
Hey @Minigugus, is there a possibility that you might update this to work properly with the latest version of Postgres.js (currently v3.3.2 as I write this)?
Here are a couple of the problems I ran into, which I've solved myself temporarily by manually altering /dist/index.js, but I'd rather my project depend on a properly updated version of this npm package instead of my patch branch:
createTableIfMissing throws an UNSAFE_TRANSACTION error since sql.begin is now required for transactions. I worked around this by manually creating the table myself.
I resolved a couple of instances of the following error by updating Date instances to strings with .toISOString():
The "string" argument must be of type string or an instance of Buffer or ArrayBuffer. Received an instance of Date
I'm not sure if there are any other issues but it appears to be working well for me now with the above workarounds. Let me know if you have any plans of officially updating this to work with v3. Thanks!
The text was updated successfully, but these errors were encountered:
Hey @Minigugus, is there a possibility that you might update this to work properly with the latest version of Postgres.js (currently v3.3.2 as I write this)?
Here are a couple of the problems I ran into, which I've solved myself temporarily by manually altering /dist/index.js, but I'd rather my project depend on a properly updated version of this npm package instead of my patch branch:
createTableIfMissing
throws an UNSAFE_TRANSACTION error since sql.begin is now required for transactions. I worked around this by manually creating the table myself.I'm not sure if there are any other issues but it appears to be working well for me now with the above workarounds. Let me know if you have any plans of officially updating this to work with v3. Thanks!
The text was updated successfully, but these errors were encountered: