How to get actual SQL query text?

[vsviridov]

I don't think the documentation ever mentions how to transform

from(Users).select('*').where(() => Users.fields.id.eq(1));

into

select * from users where id = 1;

to supply to my database driver...

Can you elaborate on this?

And how to get back the type of the resulting data, so I can inform the rest of the application about what's going on...

[vsviridov]

Btw, I've written a quick-and-dirty codegen for sqlite that produces table definitions compatible with your library...
https://gist.github.com/vsviridov/f09d82768fba96459870b80b9168f914

[ClickerMonkey]

That's pretty neat!

You can use exec function which takes a connection and creates a function that is passed a query which returns the desired types.

typed-query-builder/packages/pgsql/test/index.spec.ts

Line 149 in 2ca1d93

const name = await from(GroupTable)

[ClickerMonkey]

I don't have explicit sqlite support yet but here's an example package that is for postgres:

https://github.com/ClickerMonkey/typed-query-builder/tree/master/packages/sql-pgsql

Essentially each DB only supports certain features, functions are named different things, etc. So these sql- packages is to support the types and functions as best as possible.

[ClickerMonkey]

To get the string and type data you use a Dialect (using the base dialect may be good enough for you if you don't want to implement a Sqlite one). There are a few helper types that can be seen here. These exec functions will return different things based on the options you pass:

typed-query-builder/packages/pgsql/src/core.ts

Line 91 in 2ca1d93

export function exec<P = any>(access: PgsqlConnection, options?: PgsqlOptions<P>): <R>(expr: Expr<R>) => Promise<any>

[vsviridov]

Thank you for the fast response. Another question... As I'm planning to use it with Bun's sqlite driver, and it favors prepared statements a lot.

Is there a way to have a query builder produce a query that has named placeholder values within the query text?

Such query is cached by the sqlite engine and can be invoked with parameters in a separate call...

[ClickerMonkey]

Yep, that's by default iirc. The base dialect should support named parameters just fine.

[vsviridov]

So, the exec method seems to exist only on the Postgres package... And creating a new package for sqlite might be a bit beyond me at this stage...