Search Results for "sql connection"

In most cases clients will use the database/sql package instead of using this package directly. Similarly to libpq, when establishing a connection using pq you are expected to supply a connection string containing zero or more parameters. A subset of the connection parameters supported by libpq are also supported by pq. Additionally, pq also lets you specify run-time parameters (such as search_path or work_mem) directly in the connection string. ...

...No C-bindings, just pure Go. Connections over TCP/IPv4, TCP/IPv6, Unix domain sockets or custom protocols. Automatic handling of broken connections, as well as automatic Connection Pooling (by database/sql package). Supports queries larger than 16MB. Full sql.RawBytes support. It provides intelligent LONG DATA handling in prepared statements. Secure LOAD DATA LOCAL INFILE support with file allowlisting and io.Reader support. Optional time.Time parsing, as well as optional placeholder interpolation. db.SetConnMaxLifetime() is required to ensure connections are closed by the driver safely before connection is closed by MySQL server, OS, or other middlewares. ...

...Supports native ClickHouse TCP client-server protocol. Compatibility with database/sql (slower than native interface!). Database/sql supports http protocol for transport. (Experimental). Marshal rows into structs (ScanStruct, Select). Unmarshal struct to row (AppendStruct). Connection pool Failover and load balancing. Bulk write support (for database/sql use begin->prepare->(in loop exec)->commit). AsyncInsert, named and numeric placeholders support. ...