pgxpool.Exec vs pgxpool.Query

[Yuan325]

For the database/sql package, Query is often used for read operations and Exec is used for operations that don't return a data. Does this hold for pgxpool.Exec vs pgxpool.Query?

It seems like pgxpool.Query works for most of the operations (SELECT / UPDATE / CREATE / DROP etc.). Is there a risk for using pgxpool.Query for all operations?

[jackc]

For the database/sql package, Query is often used for read operations and Exec is used for operations that don't return a data. Does this hold for pgxpool.Exec vs pgxpool.Query?

Yes.

It seems like pgxpool.Query works for most of the operations (SELECT / UPDATE / CREATE / DROP etc.). Is there a risk for using pgxpool.Query for all operations?

It's fine. Only thing is you have to make sure the Rows returned from Query is closed either by Next() until false or by calling Close() explicitly.

All that said, while functionally you can use Query() for queries that do not return a result set, it's more idiomatic to use Exec().

[Yuan325]

Got it, thank you!