K
Kysely•11mo ago
NazCodeland

How to handle failed transactions

Hey everyone, this is not directly related to Kysely but I was wondering what is a common solution for handling failed transactions? - is it supposed to be logged somewhere so you can review it?
1 Reply
Igal
Igal•11mo ago
Hey 👋🏻 Generally in production-grade applications you'd have things monitored (+ alerts), you might have queues in between with retry mechanism + dead letter queue. dead letter queues could be consumed too for error handling - or could simply be used to investigate and re-drive later. The system could be event-sourced, so you always have the event persisted and could replay it from the event stream. returning an immediate error response without all of the stuff above ^, is also fine... it really depends on your product requirements.
Want results from more Discord servers?
Add your server
More Posts
How to generate query synchronously?Besides other things I want to use kysely to generate subqueries for sequelize scopes. Is it possiblHow to write "SELECT 1 FROM tablename"I want to create subquery for exists but don't know type select(1)...? should I use val or sql.lit oJoin using a json value with postgresI have this table: ``` export interface MzCatalogMzAuditEvents { id: Generated<string>; event_tyHow to use coalesce in a joinI'm selecting disparate object types, and then looking up details in per-type lookup tables, then I Plugin for auto-update "updated_at" fieldHello Team, Greetings! I am trying to write a plugin that will auto-update the "updated_at" column Making Transactions with KyselyAdapter for auth.jsHey everyone, I am using this KyselyAdapter package for auth.js https://github.com/nextauthjs/next-aWrong return type in raw sqlGreetings I have simple aggregations on mysql: ```typescript select([ sql`COUNT(DISTINCT r.reviewUsing `.orderBy` in JSONHey, I have a schema that roughly looks like this ```ts export interface Member { id: string;