simplify run, when only one client is used?

[Beiri22]

Describe the proposed feature
I understand why you need to call every query (select, insert,...) explicitly with a client - run(client). But for project where you only got one client; could you find a way to globally define the client and then just use run()?

[scotttrinh]

But for project where you only got one client; could you find a way to globally define the client and then just use run()?

The client instance itself is meant to be lightweight and for you to use features like .withGlobals and .withRetryOptions, etc. so even if you only define the base client once, you'll probably want to quite frequently define a derived client for certain runtime concerns like authentication. run also accepts a transaction executor.

If you want to avoid needing to pass around the client everywhere, I'd suggest looking into some kind of dependency injection setup and build out a data layer, so that in your calling code, it looks more like:

const result = await FooRepository.getAll();

instead of

const result = await e.select(e.Foo, (f) => ({
  ...f["*"],
}).run(client);

That really just moves the provisioning of the client into the FooRepository service construction, but it can make it a lot simpler in your code. In the places where you need to derive a client (to add a global for instance) you'd just override the injected client with a derived one.

As far as recommendations go, I really like Effect which gives you a really structured way of writing applications in general, but it's definitely a large toolkit meant to solve more than just dependency injection. For a more focused library, you can check out Microsoft's tsyringe project which seems like a nice API as well.

[Beiri22]

Why not a simple e.useAsDefault(...client...); and having the select with a default value, so that you can omit the client in default cases; and use it when special settings applied or a transaction is needed?