What do you want to change?
YugabyteDB PGX smart driver extend PostgreSQL drivers to enable client applications to connect to YugabyteDB clusters without the need for external load balancers.
The issue is, the connection pool created via YugabyteDB PGX smart driver does not implement db.DBTX as sqlc and YugabyteDB PGX smart driver are using pgconn.CommandTag from different packages.
Please refer to for the issue yugabyte/yugabyte-db#28996
Workaround
Inside sqlc.yaml, we can set sql_package: "yugabyte/pgx/v5". The generated code should then import github.com/yugabyte/pgx/v5, ensuring we use the same package everywhere.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go
What do you want to change?
YugabyteDB PGX smart driver extend PostgreSQL drivers to enable client applications to connect to YugabyteDB clusters without the need for external load balancers.
The issue is, the connection pool created via YugabyteDB PGX smart driver does not implement db.DBTX as sqlc and YugabyteDB PGX smart driver are using pgconn.CommandTag from different packages.
Please refer to for the issue yugabyte/yugabyte-db#28996
Workaround
Inside sqlc.yaml, we can set sql_package: "yugabyte/pgx/v5". The generated code should then import github.com/yugabyte/pgx/v5, ensuring we use the same package everywhere.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go