porsager / porsager/postgres

ReservedSql appears to have methods it does not have

Open
#713 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Typescript
Dominant language
JavaScript
Stars
8.7k
Forks
374
Avg merge
11d 16h
Merged PRs (30d)
1

Description

const sqli = await sql.reserve();
await sqli.begin(async (sql) => await sql`select 1`);
sqli.release();
// sqli.begin is not a function

Is there a technical reason transactions are not supported by reserved connections?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the sql.reserve() entry point and the ReservedSql API, then compare it with the transaction path used by sql.begin(). No files or tests are named; done means establishing whether reserved connections can support transactions and documenting or testing the resulting API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, postgresql
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.