10 Commits (9eaeb51e305fa7bed7c74a290242f9d020a55129)

Author	SHA1	Message	Date
Jack Christensen	1f4b34f932	Merge branch 'master' into v5-dev	2022-04-23 11:05:24 -05:00
Jack Christensen	f14fb3d692	Replace interface{} with any	2022-04-09 09:12:55 -05:00
Andrew Rusakow	a86ece025c	Fix single line comment for line endings in mac when sanitizing.	2022-03-04 18:17:40 -06:00
Jack Christensen	a49f4bb135	Use errors instead of golang.org/x/xerrors	2021-03-25 09:55:12 -04:00
Rusakow Andrew	292539a590	Add comment support when sanitizing SQL queries	2021-03-13 07:31:56 -06:00
Andrew Nicoll	816e95d3ee	sanatize time to within microsecond accuracy	2020-03-27 13:03:36 +00:00
Jack Christensen	29f02807b0	Restore simple protocol support	2019-05-20 20:36:03 -05:00
Jack Christensen	c53c9e6eb5	Remove simple protocol and one round trip query options ... It is impossible to guarantee that the a query executed with the simple protocol will behave the same as with the extended protocol. This is because the normal pgx path relies on knowing the OID of query parameters. Without this encoding a value can only be determined by the value instead of the combination of value and PostgreSQL type. For example, how should a []int32 be encoded? It might be encoded into a PostgreSQL int4[] or json. Removal also simplifies the core query path. The primary reason for the simple protocol is for servers like PgBouncer that may not be able to support normal prepared statements. After further research it appears that issuing a "flush" instead "sync" after preparing the unnamed statement would allow PgBouncer to work. The one round trip mode can be better handled with prepared statements. As a last resort, all original server functionality can still be accessed by dropping down to PgConn.	2019-04-13 11:39:01 -05:00
Jack Christensen	8f4178b3d3	Use github.com/pkg/errors	2017-06-04 21:30:03 -05:00
Jack Christensen	7b1f461ec3	Add simple protocol suuport with (Query|Exec)Ex	2017-04-10 08:58:51 -05:00