ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine how to guarantee that a write operation performed inside a SurrealDB transaction is not duplicated when a retry is triggered by a transient failure. Constraints SurrealDB uses optimistic concurrency control; a retry requires re‑reading the state before re‑executing the write. Without an idempotency key, a retry can produce a duplicate‑key erro
In SQL Server environments using ADO.NET, SqlCommand.CommandTimeout allows a client to send an attention signal to the server to abort a running batch when a time limit is reached. While this stops the execution of the current statement, the behavior regarding the surrounding transaction remains a point of architectural uncertainty. When a timeout occurs dur
I am setting up a repeatable development environment for a Node.js service backed by PostgreSQL, and I need to decide how Knex.js (assume a current 1.x/2.x line) should share connection management with the underlying pg driver. My understanding is that when no pool option is given, Knex builds its own generic-pool wrapper (default min 2, max 10), but when I
surrealdb
microsoftsqlserver
knexjs
postgresql