Support for Postgres (and other databases)

[flarochelleupgrade]

Would the team consider backing an implementation of support for databases other than MySQL? We would ideally run it on Postgres and the lack of support is a big drawback of this project in our tooling selection.

We could potentially contribute a pull request with some changes to get the ball rolling. However before investing any engineering effort, we need to validate that the maintainers would be open to considering, reviewing and accepting the project.

Thank you!

[flarochelleupgrade]

@tot-ra any thoughts on this?

[tot-ra]

@flarochelleupgrade hey. I think currently we don't have sufficiently large core team to maintain abstraction layer or two separate engines if SQL needs to be different (and I assume it will very likely hit differences in some areas). Especially considering new features like #146

[sijonelis]

I did some investigation on my side on this as well and it seems that knex does actually provide a sufficient abstraction layer to run postgres/mssql/sqlite, if the "raw" queries could be migrated to the knex query builder code.

@tot-ra would there be any interest from your side in PRs that would try to nudge the project this way?

One quick example of such a PR would be to use this knex feature to update such queries

await connection.raw(
    'INSERT IGNORE INTO clients_persisted_queries_rel (version_id, pq_key) VALUES (?, ?)',
    [clientVersionId, pqKey]
);

into

await connection('clients_persisted_queries_rel')
    .insert({
        version_id: clientVersionId,
        pq_key: pqKey
    })
    .onConflict('pq_key')
    ignore()

[tot-ra]

Looks like you have more traction for this
#185