go mysql driver, support distributed transaction

Related tags

Database tools mysql
Overview

Go-MySQL-Driver

A MySQL-Driver for Go's database/sql package

Go-MySQL-Driver logo



Features

  • Lightweight and fast
  • Native Go implementation. No C-bindings, just pure Go
  • Connections over TCP/IPv4, TCP/IPv6, Unix domain sockets or custom protocols
  • Automatic handling of broken connections
  • Automatic Connection Pooling (by database/sql package)
  • Supports queries larger than 16MB
  • Full sql.RawBytes support.
  • Intelligent LONG DATA handling in prepared statements
  • Secure LOAD DATA LOCAL INFILE support with file allowlisting and io.Reader support
  • Optional time.Time parsing
  • Optional placeholder interpolation

Requirements

  • Go 1.10 or higher. We aim to support the 3 latest versions of Go.
  • MySQL (4.1+), MariaDB, Percona Server, Google CloudSQL or Sphinx (2.2.3+)

Installation

Simple install the package to your $GOPATH with the go tool from shell:

$ go get -u github.com/go-sql-driver/mysql

Make sure Git is installed on your machine and in your system's PATH.

Usage

Go MySQL Driver is an implementation of Go's database/sql/driver interface. You only need to import the driver and can use the full database/sql API then.

Use mysql as driverName and a valid DSN as dataSourceName:

import (
	"database/sql"
	"time"

	_ "github.com/go-sql-driver/mysql"
)

// ...

db, err := sql.Open("mysql", "user:[email protected]/dbname")
if err != nil {
	panic(err)
}
// See "Important settings" section.
db.SetConnMaxLifetime(time.Minute * 3)
db.SetMaxOpenConns(10)
db.SetMaxIdleConns(10)

Examples are available in our Wiki.

Important settings

db.SetConnMaxLifetime() is required to ensure connections are closed by the driver safely before connection is closed by MySQL server, OS, or other middlewares. Since some middlewares close idle connections by 5 minutes, we recommend timeout shorter than 5 minutes. This setting helps load balancing and changing system variables too.

db.SetMaxOpenConns() is highly recommended to limit the number of connection used by the application. There is no recommended limit number because it depends on application and MySQL server.

db.SetMaxIdleConns() is recommended to be set same to (or greater than) db.SetMaxOpenConns(). When it is smaller than SetMaxOpenConns(), connections can be opened and closed very frequently than you expect. Idle connections can be closed by the db.SetConnMaxLifetime(). If you want to close idle connections more rapidly, you can use db.SetConnMaxIdleTime() since Go 1.15.

DSN (Data Source Name)

The Data Source Name has a common format, like e.g. PEAR DB uses it, but without type-prefix (optional parts marked by squared brackets):

[username[:password]@][protocol[(address)]]/dbname[?param1=value1&...&paramN=valueN]

A DSN in its fullest form:

username:[email protected](address)/dbname?param=value

Except for the databasename, all values are optional. So the minimal DSN is:

/dbname

If you do not want to preselect a database, leave dbname empty:

/

This has the same effect as an empty DSN string:


Alternatively, Config.FormatDSN can be used to create a DSN string by filling a struct.

Password

Passwords can consist of any character. Escaping is not necessary.

Protocol

See net.Dial for more information which networks are available. In general you should use an Unix domain socket if available and TCP otherwise for best performance.

Address

For TCP and UDP networks, addresses have the form host[:port]. If port is omitted, the default port will be used. If host is a literal IPv6 address, it must be enclosed in square brackets. The functions net.JoinHostPort and net.SplitHostPort manipulate addresses in this form.

For Unix domain sockets the address is the absolute path to the MySQL-Server-socket, e.g. /var/run/mysqld/mysqld.sock or /tmp/mysql.sock.

Parameters

Parameters are case-sensitive!

Notice that any of true, TRUE, True or 1 is accepted to stand for a true boolean value. Not surprisingly, false can be specified as any of: false, FALSE, False or 0.

allowAllFiles
Type:           bool
Valid Values:   true, false
Default:        false

allowAllFiles=true disables the file allowlist for LOAD DATA LOCAL INFILE and allows all files. Might be insecure!

allowCleartextPasswords
Type:           bool
Valid Values:   true, false
Default:        false

allowCleartextPasswords=true allows using the cleartext client side plugin if required by an account, such as one defined with the PAM authentication plugin. Sending passwords in clear text may be a security problem in some configurations. To avoid problems if there is any possibility that the password would be intercepted, clients should connect to MySQL Server using a method that protects the password. Possibilities include TLS / SSL, IPsec, or a private network.

allowNativePasswords
Type:           bool
Valid Values:   true, false
Default:        true

allowNativePasswords=false disallows the usage of MySQL native password method.

allowOldPasswords
Type:           bool
Valid Values:   true, false
Default:        false

allowOldPasswords=true allows the usage of the insecure old password method. This should be avoided, but is necessary in some cases. See also the old_passwords wiki page.

charset
Type:           string
Valid Values:   <name>
Default:        none

Sets the charset used for client-server interaction ("SET NAMES <value>"). If multiple charsets are set (separated by a comma), the following charset is used if setting the charset failes. This enables for example support for utf8mb4 (introduced in MySQL 5.5.3) with fallback to utf8 for older servers (charset=utf8mb4,utf8).

Usage of the charset parameter is discouraged because it issues additional queries to the server. Unless you need the fallback behavior, please use collation instead.

checkConnLiveness
Type:           bool
Valid Values:   true, false
Default:        true

On supported platforms connections retrieved from the connection pool are checked for liveness before using them. If the check fails, the respective connection is marked as bad and the query retried with another connection. checkConnLiveness=false disables this liveness check of connections.

collation
Type:           string
Valid Values:   <name>
Default:        utf8mb4_general_ci

Sets the collation used for client-server interaction on connection. In contrast to charset, collation does not issue additional queries. If the specified collation is unavailable on the target server, the connection will fail.

A list of valid charsets for a server is retrievable with SHOW COLLATION.

The default collation (utf8mb4_general_ci) is supported from MySQL 5.5. You should use an older collation (e.g. utf8_general_ci) for older MySQL.

Collations for charset "ucs2", "utf16", "utf16le", and "utf32" can not be used (ref).

clientFoundRows
Type:           bool
Valid Values:   true, false
Default:        false

clientFoundRows=true causes an UPDATE to return the number of matching rows instead of the number of rows changed.

columnsWithAlias
Type:           bool
Valid Values:   true, false
Default:        false

When columnsWithAlias is true, calls to sql.Rows.Columns() will return the table alias and the column name separated by a dot. For example:

SELECT u.id FROM users as u

will return u.id instead of just id if columnsWithAlias=true.

interpolateParams
Type:           bool
Valid Values:   true, false
Default:        false

If interpolateParams is true, placeholders (?) in calls to db.Query() and db.Exec() are interpolated into a single query string with given parameters. This reduces the number of roundtrips, since the driver has to prepare a statement, execute it with given parameters and close the statement again with interpolateParams=false.

This can not be used together with the multibyte encodings BIG5, CP932, GB2312, GBK or SJIS. These are rejected as they may introduce a SQL injection vulnerability!

loc
Type:           string
Valid Values:   <escaped name>
Default:        UTC

Sets the location for time.Time values (when using parseTime=true). "Local" sets the system's location. See time.LoadLocation for details.

Note that this sets the location for time.Time values but does not change MySQL's time_zone setting. For that see the time_zone system variable, which can also be set as a DSN parameter.

Please keep in mind, that param values must be url.QueryEscape'ed. Alternatively you can manually replace the / with %2F. For example US/Pacific would be loc=US%2FPacific.

maxAllowedPacket
Type:          decimal number
Default:       4194304

Max packet size allowed in bytes. The default value is 4 MiB and should be adjusted to match the server settings. maxAllowedPacket=0 can be used to automatically fetch the max_allowed_packet variable from server on every connection.

multiStatements
Type:           bool
Valid Values:   true, false
Default:        false

Allow multiple statements in one query. While this allows batch queries, it also greatly increases the risk of SQL injections. Only the result of the first query is returned, all other results are silently discarded.

When multiStatements is used, ? parameters must only be used in the first statement.

parseTime
Type:           bool
Valid Values:   true, false
Default:        false

parseTime=true changes the output type of DATE and DATETIME values to time.Time instead of []byte / string The date or datetime like 0000-00-00 00:00:00 is converted into zero value of time.Time.

readTimeout
Type:           duration
Default:        0

I/O read timeout. The value must be a decimal number with a unit suffix ("ms", "s", "m", "h"), such as "30s", "0.5m" or "1m30s".

rejectReadOnly
Type:           bool
Valid Values:   true, false
Default:        false

rejectReadOnly=true causes the driver to reject read-only connections. This is for a possible race condition during an automatic failover, where the mysql client gets connected to a read-only replica after the failover.

Note that this should be a fairly rare case, as an automatic failover normally happens when the primary is down, and the race condition shouldn't happen unless it comes back up online as soon as the failover is kicked off. On the other hand, when this happens, a MySQL application can get stuck on a read-only connection until restarted. It is however fairly easy to reproduce, for example, using a manual failover on AWS Aurora's MySQL-compatible cluster.

If you are not relying on read-only transactions to reject writes that aren't supposed to happen, setting this on some MySQL providers (such as AWS Aurora) is safer for failovers.

Note that ERROR 1290 can be returned for a read-only server and this option will cause a retry for that error. However the same error number is used for some other cases. You should ensure your application will never cause an ERROR 1290 except for read-only mode when enabling this option.

serverPubKey
Type:           string
Valid Values:   <name>
Default:        none

Server public keys can be registered with mysql.RegisterServerPubKey, which can then be used by the assigned name in the DSN. Public keys are used to transmit encrypted data, e.g. for authentication. If the server's public key is known, it should be set manually to avoid expensive and potentially insecure transmissions of the public key from the server to the client each time it is required.

timeout
Type:           duration
Default:        OS default

Timeout for establishing connections, aka dial timeout. The value must be a decimal number with a unit suffix ("ms", "s", "m", "h"), such as "30s", "0.5m" or "1m30s".

tls
Type:           bool / string
Valid Values:   true, false, skip-verify, preferred, <name>
Default:        false

tls=true enables TLS / SSL encrypted connection to the server. Use skip-verify if you want to use a self-signed or invalid certificate (server side) or use preferred to use TLS only when advertised by the server. This is similar to skip-verify, but additionally allows a fallback to a connection which is not encrypted. Neither skip-verify nor preferred add any reliable security. You can use a custom TLS config after registering it with mysql.RegisterTLSConfig.

writeTimeout
Type:           duration
Default:        0

I/O write timeout. The value must be a decimal number with a unit suffix ("ms", "s", "m", "h"), such as "30s", "0.5m" or "1m30s".

System Variables

Any other parameters are interpreted as system variables:

  • <boolean_var>=<value>: SET <boolean_var>=<value>
  • <enum_var>=<value>: SET <enum_var>=<value>
  • <string_var>=%27<value>%27: SET <string_var>='<value>'

Rules:

  • The values for string variables must be quoted with '.
  • The values must also be url.QueryEscape'ed! (which implies values of string variables must be wrapped with %27).

Examples:

Examples

[email protected](/path/to/socket)/dbname
root:[email protected](/tmp/mysql.sock)/myDatabase?loc=Local
user:[email protected](localhost:5555)/dbname?tls=skip-verify&autocommit=true

Treat warnings as errors by setting the system variable sql_mode:

user:[email protected]/dbname?sql_mode=TRADITIONAL

TCP via IPv6:

user:[email protected]([de:ad:be:ef::ca:fe]:80)/dbname?timeout=90s&collation=utf8mb4_unicode_ci

TCP on a remote host, e.g. Amazon RDS:

id:[email protected](your-amazonaws-uri.com:3306)/dbname

Google Cloud SQL on App Engine:

user:[email protected](/cloudsql/project-id:region-name:instance-name)/dbname

TCP using default port (3306) on localhost:

user:[email protected]/dbname?charset=utf8mb4,utf8&sys_var=esc%40ped

Use the default protocol (tcp) and host (localhost:3306):

user:[email protected]/dbname

No Database preselected:

user:[email protected]/

Connection pool and timeouts

The connection pool is managed by Go's database/sql package. For details on how to configure the size of the pool and how long connections stay in the pool see *DB.SetMaxOpenConns, *DB.SetMaxIdleConns, and *DB.SetConnMaxLifetime in the database/sql documentation. The read, write, and dial timeouts for each individual connection are configured with the DSN parameters readTimeout, writeTimeout, and timeout, respectively.

ColumnType Support

This driver supports the ColumnType interface introduced in Go 1.8, with the exception of ColumnType.Length(), which is currently not supported.

context.Context Support

Go 1.8 added database/sql support for context.Context. This driver supports query timeouts and cancellation via contexts. See context support in the database/sql package for more details.

LOAD DATA LOCAL INFILE support

For this feature you need direct access to the package. Therefore you must change the import path (no _):

import "github.com/go-sql-driver/mysql"

Files must be explicitly allowed by registering them with mysql.RegisterLocalFile(filepath) (recommended) or the allowlist check must be deactivated by using the DSN parameter allowAllFiles=true (Might be insecure!).

To use a io.Reader a handler function must be registered with mysql.RegisterReaderHandler(name, handler) which returns a io.Reader or io.ReadCloser. The Reader is available with the filepath Reader::<name> then. Choose different names for different handlers and DeregisterReaderHandler when you don't need it anymore.

See the godoc of Go-MySQL-Driver for details.

time.Time support

The default internal output type of MySQL DATE and DATETIME values is []byte which allows you to scan the value into a []byte, string or sql.RawBytes variable in your program.

However, many want to scan MySQL DATE and DATETIME values into time.Time variables, which is the logical equivalent in Go to DATE and DATETIME in MySQL. You can do that by changing the internal output type from []byte to time.Time with the DSN parameter parseTime=true. You can set the default time.Time location with the loc DSN parameter.

Caution: As of Go 1.1, this makes time.Time the only variable type you can scan DATE and DATETIME values into. This breaks for example sql.RawBytes support.

Unicode support

Since version 1.5 Go-MySQL-Driver automatically uses the collation utf8mb4_general_ci by default.

Other collations / charsets can be set using the collation DSN parameter.

Version 1.0 of the driver recommended adding &charset=utf8 (alias for SET NAMES utf8) to the DSN to enable proper UTF-8 support. This is not necessary anymore. The collation parameter should be preferred to set another collation / charset than the default.

See http://dev.mysql.com/doc/refman/8.0/en/charset-unicode.html for more details on MySQL's Unicode support.

Testing / Development

To run the driver tests you may need to adjust the configuration. See the Testing Wiki-Page for details.

Go-MySQL-Driver is not feature-complete yet. Your help is very appreciated. If you want to contribute, you can work on an open issue or review a pull request.

See the Contribution Guidelines for details.


License

Go-MySQL-Driver is licensed under the Mozilla Public License Version 2.0

Mozilla summarizes the license scope as follows:

MPL: The copyleft applies to any files containing MPLed code.

That means:

  • You can use the unchanged source code both in private and commercially.
  • When distributing, you must publish the source code of any changed files licensed under the MPL 2.0 under a) the MPL 2.0 itself or b) a compatible license (e.g. GPL 3.0 or Apache License 2.0).
  • You needn't publish the source code of your library as long as the files licensed under the MPL 2.0 are unchanged.

Please read the MPL 2.0 FAQ if you have further questions regarding the license.

You can read the full terms here: LICENSE.

Go Gopher and MySQL Dolphin

Comments
  • skip_check_lock

    skip_check_lock

    Description

    refer to this issue I will pull request to seata-golang, too.

    Checklist

    • [ ] Code compiles correctly
    • [ ] Created tests which fail without the change (if possible)
    • [ ] All tests passing
    • [ ] Extended the README / documentation, if necessary
    • [ ] Added myself / the copyright holder to the AUTHORS file
    opened by xjlgod 3
  • [bug] unique index error when rolling back

    [bug] unique index error when rolling back

    Issue description

    pk is primary key v1 + v2 is unique index

    pk, v1, v2
    -----------
    1,  4,  8
    

    bug scenario:

    phase1 -> local commit
    	step 1:
    		pk, v1, v2
    		-----------
    		1,  4,  8   -> delete
    
    	step 2:
    		pk, v1, v2
    		-----------
    		2,  4,  8   -> insert
    
    phase2 -> branch rollback
    	step 3:
    		pk, v1, v2
    		-----------
    		1,  4,  8   -> insert    ->   unique index error
    
    	step 4:
    		pk, v1, v2
    		-----------
    		2,  4,  8   -> delete
    

    The correct branch rollback order should be:

    phase2 -> branch rollback
    	step 3:
    		pk, v1, v2
    		-----------
    		2,  4,  8   -> delete
    
    	step 4:
    		pk, v1, v2
    		-----------
    		1,  4,  8   -> insert
    

    Example code

    Error log

    Configuration

    opened by bohehe 1
  • optimize build UndoItem logic

    optimize build UndoItem logic

    Issue description

    refer: https://github.com/seata/seata/issues/4280, the version of go can be optimize eithor, the code is as follow.

    func (executor *insertExecutor) Execute() (driver.Result, error) {
    	beforeImage, err := executor.BeforeImage()
    	if err != nil {
    		return nil, err
    	}
    	result, err := executor.mc.execAlways(executor.originalSQL, executor.args)
    	if err != nil {
    		return result, err
    	}
    
    	afterImage, err := executor.AfterImage(result)
    
    	if err != nil {
    		return nil, err
    	}
    	executor.PrepareUndoLog(beforeImage, afterImage)
    	return result, err
    }
    

    If you want to optimize it, please comment "Please assign it to me" in this issue. 如果有兴趣优化的,可以在下方留言please assign it to me

    opened by caohdgege 1
  • perf: If updateExcutor affect 0 row, let afterImage equal beforeImage.

    perf: If updateExcutor affect 0 row, let afterImage equal beforeImage.

    Description

    • fix #3
    • For updateExcutor, if rowAffect=0, let afterImage equal beforeImage.

    Checklist

    • [x] Code compiles correctly
    • [x] Created tests which fail without the change (if possible)
    • [x] All tests passing
    • [x] Extended the README / documentation, if necessary
    • [x] Added myself / the copyright holder to the AUTHORS file
    opened by sheny1xuan 0
  • 更新查询information_schema columns 部分数据类型由int32变更为int64

    更新查询information_schema columns 部分数据类型由int32变更为int64

    Description

    原因: 当模型表中string 类型未定义长度时,information_schema 库中 COLUMNS表中CHARACTER_MAXIMUM_LENGTH 长度是一个很大的int64值,而在代码中schema 对应的定义成int32,会存在类型转换不通过的问题

    Checklist_

    • [ ] Code compiles correctly
    • [ ] Created tests which fail without the change (if possible)
    • [ ] All tests passing
    • [ ] Extended the README / documentation, if necessary
    • [ ] Added myself / the copyright holder to the AUTHORS file
    opened by slowmoon 0
  • V1.1.1

    V1.1.1

    Description

    Please explain the changes you made here.

    Checklist

    • [ ] Code compiles correctly
    • [ ] Created tests which fail without the change (if possible)
    • [ ] All tests passing
    • [ ] Extended the README / documentation, if necessary
    • [ ] Added myself / the copyright holder to the AUTHORS file
    opened by slowmoon 0
  • 阅读源码时的一点疑问?

    阅读源码时的一点疑问?

    Issue description

    关于undo_log的记录我只在stmt下看到了,但是“database/sql”包里Tx的Exec函数默认会优先调用driverConn的ExecContext,也就是mysqlConn的ExecContext,但这个函数里面并有undo_log相关的处理。是我哪里理解有问题么?

    opened by importcjj 1
  • undo_log时区问题

    undo_log时区问题

    Issue description

    mysql,表里包含timestamp字段时,回滚会失败,报错是:“ERROR check dirty datas failed, old and new data are not equal” timestamp类型的字段都会不一致

    Error log

    2022-03-21T01:06:57.279+0800	ERROR	check dirty datas failed, old and new data are not equal, tableName:[`jt_erp_inventory`], oldRows:[[{"Fields":[{"Name":"id","KeyType":1,"Type":-5,"Value":403},{"Name":"user_id","KeyType":0,"Type":0,"Value":1011},{"Name":"operator_id","KeyType":0,"Type":0,"Value":1011},{"Name":"warehouse_id","KeyType":0,"Type":0,"Value":91},{"Name":"product_id","KeyType":0,"Type":0,"Value":41209},{"Name":"sku","KeyType":0,"Type":12,"Value":"QzA3MDgxNC0y"},{"Name":"useable_num","KeyType":0,"Type":0,"Value":9},{"Name":"order_lock_num","KeyType":0,"Type":0,"Value":1},{"Name":"pre_on_shelf","KeyType":0,"Type":0,"Value":0},{"Name":"on_shelf","KeyType":0,"Type":0,"Value":0},{"Name":"pre_out","KeyType":0,"Type":0,"Value":0},{"Name":"defective","KeyType":0,"Type":0,"Value":0},{"Name":"defective_pre_out","KeyType":0,"Type":0,"Value":0},{"Name":"on_way","KeyType":0,"Type":0,"Value":2},{"Name":"less","KeyType":0,"Type":0,"Value":0},{"Name":"less_start_time","KeyType":0,"Type":93,"Value":null},{"Name":"version","KeyType":0,"Type":0,"Value":23},{"Name":"create_time","KeyType":0,"Type":93,"Value":"2022-03-15T23:49:36+08:00"},{"Name":"last_update_time","KeyType":0,"Type":93,"Value":"2022-03-21T08:53:02+08:00"}]}]], newRows:[[{"Fields":[{"Name":"id","KeyType":1,"Type":-5,"Value":403},{"Name":"user_id","KeyType":0,"Type":0,"Value":1011},{"Name":"operator_id","KeyType":0,"Type":0,"Value":1011},{"Name":"warehouse_id","KeyType":0,"Type":0,"Value":91},{"Name":"product_id","KeyType":0,"Type":0,"Value":41209},{"Name":"sku","KeyType":0,"Type":12,"Value":"QzA3MDgxNC0y"},{"Name":"useable_num","KeyType":0,"Type":0,"Value":9},{"Name":"order_lock_num","KeyType":0,"Type":0,"Value":1},{"Name":"pre_on_shelf","KeyType":0,"Type":0,"Value":0},{"Name":"on_shelf","KeyType":0,"Type":0,"Value":0},{"Name":"pre_out","KeyType":0,"Type":0,"Value":0},{"Name":"defective","KeyType":0,"Type":0,"Value":0},{"Name":"defective_pre_out","KeyType":0,"Type":0,"Value":0},{"Name":"on_way","KeyType":0,"Type":0,"Value":2},{"Name":"less","KeyType":0,"Type":0,"Value":0},{"Name":"less_start_time","KeyType":0,"Type":93,"Value":null},{"Name":"version","KeyType":0,"Type":0,"Value":23},{"Name":"create_time","KeyType":0,"Type":93,"Value":"2022-03-15T15:49:36+08:00"},{"Name":"last_update_time","KeyType":0,"Type":93,"Value":"2022-03-21T00:53:02+08:00"}]}]].
    2022-03-21T01:06:57.290+0800	ERROR	[stacktrace]branchRollback failed. xid:[aggSvc:9250340230840323], branchID:[9250340230840324], resourceID:[jt_inv_0001], branchType:[0], applicationData:[[]]
    2022-03-21T01:06:57.290+0800	ERROR	Has dirty records when undo.
    

    Configuration

    Driver version (or git SHA):

    *Go version: go1.17

    *Server version: MySQL 5.7.18

    *Server OS: OSX 11.5.2

    opened by xiaxiaosheng 1
Releases(v2.0.7)
Owner
Open Transaction
Transactional Specification
Open Transaction
a lightweight distributed transaction management service, support xa tcc saga

a lightweight distributed transaction management service, support xa tcc saga

null 7.9k Nov 28, 2022
Go-driver-benchmark - Driver benchmark with golang

We use ClickkHouse for time-series databases, and the driver's performance is ve

null 4 Sep 5, 2022
mysql to mysql 轻量级多线程的库表数据同步

goMysqlSync golang mysql to mysql 轻量级多线程库表级数据同步 测试运行 设置当前binlog位置并且开始运行 go run main.go -position mysql-bin.000001 1 1619431429 查询当前binlog位置,参数n为秒数,查询结

null 14 Nov 15, 2022
MySQL Storage engine conversion,Support mutual conversion between MyISAM and InnoDB engines.

econvert MySQL Storage engine conversion 简介 此工具用于MySQL存储引擎转换,支持CTAS和ALTER两种模式,目前只支持MyISAM和InnoDB存储引擎相互转换,其它引擎尚不支持。 注意:当对表进行引擎转换时,建议业务停止访问或者极少量访问时进行。 原

null 5 Oct 25, 2021
Support MySQL or MariaDB for gopsql/psql and gopsql/db

mysql Support MySQL or MariaDB for github.com/gopsql/psql. You can make MySQL SELECT, INSERT, UPDATE, DELETE statements with this package. NOTE: Pleas

null 0 Dec 9, 2021
SQL transaction wrapper on golang

TxWrapper TxWrapper is a sql transaction wrapper. It helps to exclude writing code for rollback and commit commands. Usage import ( "context"

Dmitry Stoletoff 1 Mar 14, 2022
The MongoDB driver for Go

The MongoDB driver for Go This fork has had a few improvements by ourselves as well as several PR's merged from the original mgo repo that are current

GlobalSign 2k Nov 30, 2022
A fully-featured AWS Athena database driver (+ athenareader https://github.com/uber/athenadriver/tree/master/athenareader)

?? athenadriver - A fully-featured AWS Athena database driver for Go ?? athenareader - A moneywise command line utililty to query athena in command li

Uber Open Source 116 Oct 23, 2022
Apache H2 Database Go Driver

Apache H2 Database Go Driver This driver is VERY experimental state NOT use for production yet Introduction Apache H2 Database is a very-low footprint

JM Robles 39 Oct 26, 2022
sqlcomment is an ent driver that adds SQL comments following sqlcommenter specification.

sqlcomment sqlcomment is an ent driver that adds SQL comments following sqlcommenter specification. sqlcomment includes support for OpenTelemetry and

ariga 52 Nov 14, 2022
Attach hooks to any database/sql driver

sqlhooks Attach hooks to any database/sql driver. The purpose of sqlhooks is to provide a way to instrument your sql statements, making really easy to

Gustavo Chaín 595 Nov 30, 2022
Golang database driver for SQLite

go-sqlite Golang database driver for SQLite. Does not use cgo. This driver is based on pure-Go SQLite implementation (https://gitlab.com/cznic/sqlite)

glebarez 147 Nov 20, 2022
BigQuery database/sql golang driver

BigQuery SQL Driver This library is compatible with Go 1.17+ Please refer to CHA

Viant, Inc 6 Aug 31, 2022
Otelsql - OpenTelemetry SQL database driver wrapper for Go

OpenTelemetry SQL database driver wrapper for Go Add a OpenTelemetry wrapper to

Nhat 37 Nov 29, 2022
Google Cloud Spanner driver for Go's database/sql package.

go-sql-spanner Google Cloud Spanner driver for Go's database/sql package. This support is currently in the Preview release status. import _ "github.co

Google APIs 77 Nov 22, 2022
a powerful mysql toolset with Go

go-mysql A pure go library to handle MySQL network protocol and replication. Call for Committer/Maintainer Sorry that I have no enough time to maintai

siddontang 3.9k Nov 28, 2022
Sync MySQL data into elasticsearch

go-mysql-elasticsearch is a service syncing your MySQL data into Elasticsearch automatically. It uses mysqldump to fetch the origin data at first, the

siddontang 3.9k Nov 27, 2022
A high-performance MySQL proxy

kingshard 中文主页 Overview kingshard is a high-performance proxy for MySQL powered by Go. Just like other mysql proxies, you can use it to split the read

Fei Chen 6.1k Nov 28, 2022
Golang MySql binary log replication listener

Go MySql binary log replication listener Pure Go Implementation of MySQL replication protocol. This allow you to receive event like insert, update, de

Pavel <Ven> Gulbin 189 Oct 25, 2022