Support for pgx / pgxpool PostgreSQL

[zeroallox]

Greetings,

I would love to use SQLBoiler with the native pgx / pgxpool PostgreSQL driver

https://github.com/jackc/pgx

One can already do this via their pgx <> stdlib wrapper however you're then stuck with the limitations of the database/sql interface.

See: https://github.com/jackc/pgx#choosing-between-the-pgx-and-databasesql-interfaces

[stephenafamo]

In theory, all that is needed to be able to use any of that in the boil methods is to implement the boil.ContextExecutor interface.
Since it is only a few methods (2 I think), if it doesn't already satisfy the interface, you could easily create a wrapper around it.

Once that is done, you can pass it into any of the boil methods.

[zeroallox]

Thanks for the reply!

I gave this a fiddle today...

Creating a wrapper around sql.Result is doable as that's an interface.

Having my wrapper return concrete *sql.Row and *sql.Row does not seem possible as these are concrete types defined in database/sql

First attempt:
https://gist.github.com/zeroallox/b655b5849aa4ea4bd24767a6e80e6b19

[stephenafamo]

This is interesting. Perhaps in sqlboiler/v5 instead of directly using sql.Row and sql.Rows we could use an interface that these satisfy instead.
That should make it easier to wrap around.

In the meantime, this seems like a blocker.

[zeroallox]

Ahh, ok, no problem!

What I've ended up doing is to use queries.BuildQuery(query) on the return of models.NewQuery(...mods), models.SomeObject(...mods) etc and then send the raw statement to pgx and then rows.Scan() as normal. This allows me to half use SQLBoiler as intended.

My largest operations are mass inserts (using pgx's support for COPY) or mass reads (done as described above). So it's not like i'm sending zillions small operations quickly to where it matters.

So it's kind of worked out actually :P

It would be dandy though if SQLBoiler did indeed take an interface as you were suggesting.

Thank you so much for the help and feedback! <3