Kysely transactions

[vercel]

Kysely transactions

[emirotin]

Yeah, this was much unexpected, after I've invested some time into tailoring my code to run with Vercel serverless functions and Vercel PG

[vvo]

Hey @roelandmoors and @emirotin have you tried to use the original transaction example from Kysely as seen here: https://kysely.dev/docs/examples/transactions/simple-transaction? Let me know how it goes

[emirotin]

@vvo nope, instantly switched to another PG provider, transactions are crucial for my use-case

[roelandmoors]

Sorry, I don't remember. I'm using a different stack now.
But how could it work if it is not implemented? (kysely_transactions_not_supported)

[vvo]

Sorry, I don't remember. I'm using a different stack now.

Well I am just wondering if this was the right method (beginTransaction) to use versus the current kysely documentation which says to use .transaction. i.e. it might just works nowadays.

Closing, let's wait for someone else to come about this.

[emirotin]

@vvo pretty sure I was following the Kysely docs, I believe beginTransaction is being called by the transaction method

[jswent]

Is there still nothing done on this? This library is essentially useless to me if transactions are not supported.

@emirotin what provider did you switch to for Vercel PG?

[emirotin]

It was claimed that it should work https://x.com/cramforce/status/1713185661996707987?s=20, yet my followup Q was unanswered. I switched to fly.io, works nicely so far.

…

On Thu, Nov 30, 2023, 19:11 James Swent ***@***.***> wrote: Is there still nothing done on this? This library is essentially useless to me if transactions are not supported. @emirotin <https://github.com/emirotin> what provider did you switch to for Vercel PG? — Reply to this email directly, view it on GitHub <#162 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEAMCGA5XAOOORUAZEOSKDYHC44RAVCNFSM6AAAAAAYIRWCZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGE4DQNRTGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>