chore: use literal for limits and offsets

[staaldraad]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Limits and offsets are typed as Number but are treated as string in SQL template generation

What is the new behavior?

Treats these as literals so the SQL will always be correct / valid.

Additional context

Add any other context or screenshots.

[avallete]

We do the escaping for filterByValue and filterByList even tough at the end of the day postgres-meta is meant to execute queries on database that the user already has access to.

Since the pattern is so similar everywhere, we might consider normalizing this into an helper. That can be done as a follow-up tough.

[staaldraad]

We do the escaping for filterByValue and filterByList even tough at the end of the day postgres-meta is meant to execute queries on database that the user already has access to.Since the pattern is so similar everywhere, we might consider normalizing this into an helper. That can be done as a follow-up tough.

postgres-meta is meant to execute queries on database that the user already has access to

💯 agree, there are some endpoints though that have unexpected side effects, for example config.sql.ts can be called as:

http://127.0.0.1/config?limit=1%3BCREATE%20TABLE....

Pipeline-ing the create table... statement with the config read operation. This just tightens things up a little bit