github.com/go-ozzo/ozzo-dbx
ozzo-dbx is a Go package that enhances the standard database/sql package by providing powerful data retrieval methods
as well as DB-agnostic query building capabilities. ozzo-dbx is not an ORM. It has the following features:
Go 1.13 or above.
Run the following command to install the package:
go get github.com/go-ozzo/ozzo-dbx
In addition, install the specific DB driver package for the kind of database to be used. Please refer to SQL database drivers for a complete list. For example, if you are using MySQL, you may install the following package:
go get github.com/go-sql-driver/mysql
and import it in your main code like the following:
import _ "github.com/go-sql-driver/mysql"
The following databases are fully supported out of box:
For other databases, the query building feature may not work as expected. You can create a custom builder to solve the problem. Please see the last section for more details.
The following code snippet shows how you can use this package in order to access data from a MySQL database.
import (
"fmt"
"github.com/go-ozzo/ozzo-dbx"
_ "github.com/go-sql-driver/mysql"
)
func main() {
db, _ := dbx.Open("mysql", "user:pass@/example")
// create a new query
q := db.NewQuery("SELECT id, name FROM users LIMIT 10")
// fetch all rows into a struct array
var users []struct {
ID, Name string
}
err := q.All(&users)
// fetch a single row into a struct
var user struct {
ID, Name string
}
err = q.One(&user)
// fetch a single row into a string map
data := dbx.NullStringMap{}
err = q.One(data)
// fetch row by row
rows2, _ := q.Rows()
for rows2.Next() {
_ = rows2.ScanStruct(&user)
// rows.ScanMap(data)
// rows.Scan(&id, &name)
}
}
And the following example shows how to use the query building capability of this package.
import (
"fmt"
"github.com/go-ozzo/ozzo-dbx"
_ "github.com/go-sql-driver/mysql"
)
func main() {
db, _ := dbx.Open("mysql", "user:pass@/example")
// build a SELECT query
// SELECT `id`, `name` FROM `users` WHERE `name` LIKE '%Charles%' ORDER BY `id`
q := db.Select("id", "name").
From("users").
Where(dbx.Like("name", "Charles")).
OrderBy("id")
// fetch all rows into a struct array
var users []struct {
ID, Name string
}
err := q.All(&users)
// build an INSERT query
// INSERT INTO `users` (`name`) VALUES ('James')
err = db.Insert("users", dbx.Params{
"name": "James",
}).Execute()
}
To connect to a database, call dbx.Open() in the same way as you would do with the Open() method in database/sql.
db, err := dbx.Open("mysql", "user:pass@hostname/db_name")
The method returns a dbx.DB instance which can be used to create and execute DB queries. Note that the method
does not really establish a connection until a query is made using the returned dbx.DB instance. It also
does not check the correctness of the data source name either. Call dbx.MustOpen() to make sure the data
source name is correct.
To execute a SQL statement, first create a dbx.Query instance by calling DB.NewQuery() with the SQL statement
to be executed. And then call Query.Execute() to execute the query if the query is not meant to retrieving data.
For example,
q := db.NewQuery("UPDATE users SET status=1 WHERE id=100")
result, err := q.Execute()
If the SQL statement does retrieve data (e.g. a SELECT statement), one of the following methods should be called, which will execute the query and populate the result into the specified variable(s).
Query.All(): populate all rows of the result into a slice of structs or NullString maps.Query.One(): populate the first row of the result into a struct or a NullString map.Query.Column(): populate the first column of the result into a slice.Query.Row(): populate the first row of the result into a list of variables, one for each returning column.Query.Rows(): returns a dbx.Rows instance to allow retrieving data row by row.For example,
type User struct {
ID int
Name string
}
var (
users []User
user User
row dbx.NullStringMap
id int
name string
err error
)
q := db.NewQuery("SELECT id, name FROM users LIMIT 10")
// populate all rows into a User slice
err = q.All(&users)
fmt.Println(users[0].ID, users[0].Name)
// populate the first row into a User struct
err = q.One(&user)
fmt.Println(user.ID, user.Name)
// populate the first row into a NullString map
err = q.One(&row)
fmt.Println(row["id"], row["name"])
var ids []int
err = q.Column(&ids)
fmt.Println(ids)
// populate the first row into id and name
err = q.Row(&id, &name)
// populate data row by row
rows, _ := q.Rows()
for rows.Next() {
_ = rows.ScanMap(&row)
}
When populating a struct, the following rules are used to determine which columns should go into which struct fields:
Query.FieldMapper.
The default field mapping function separates words in a field name by underscores and turns them into lower case.
For example, a field name FirstName will be mapped to the column name first_name, and MyID to my_id.db tag, the tag value will be used as the corresponding column name. If the db tag is a dash -,
it means the field should NOT be populated.An exception to the above struct expansion is that when a struct type implements sql.Scanner or when it is time.Time.
In this case, the field will be populated as a whole by the DB driver. Also, if a field is a pointer to some type,
the field will be allocated memory and populated with the query result if it is not null.
The following example shows how fields are populated according to the rules above:
type User struct {
id int
Type int `db:"-"`
MyName string `db:"name"`
Profile
Address Address `db:"addr"`
}
type Profile struct {
Age int
}
type Address struct {
City string
}
User.id: not populated because the field is not exported;User.Type: not populated because the db tag is -;User.MyName: to be populated from the name column, according to the db tag;Profile.Age: to be populated from the age column, since Profile is an anonymous field;Address.City: to be populated from the addr.city column, since Address is a named field of struct type
and its fields will be prefixed with addr. according to the db tag.Note that if a column in the result does not have a corresponding struct field, it will be ignored. Similarly, if a struct field does not have a corresponding column in the result, it will not be populated.
A SQL statement is usually parameterized with dynamic values. For example, you may want to select the user record
according to the user ID received from the client. Parameter binding should be used in this case, and it is almost
always preferred to prevent from SQL injection attacks. Unlike database/sql which does anonymous parameter binding,
ozzo-dbx uses named parameter binding. Anonymous parameter binding is not supported, as it will mess up with named
parameters. For example,
q := db.NewQuery("SELECT id, name FROM users WHERE id={:id}")
q.Bind(dbx.Params{"id": 100})
err := q.One(&user)
The above example will select the user record whose id is 100. The method Query.Bind() binds a set
of named parameters to a SQL statement which contains parameter placeholders in the format of {:ParamName}.
If a SQL statement needs to be executed multiple times with different parameter values, it may be prepared to improve the performance. For example,
q := db.NewQuery("SELECT id, name FROM users WHERE id={:id}")
q.Prepare()
defer q.Close()
q.Bind(dbx.Params{"id": 100})
err := q.One(&user)
q.Bind(dbx.Params{"id": 200})
err = q.One(&user)
// ...
Queries are cancelable when they are used with context.Context. In particular, by calling Query.WithContext() you
can associate a context with a query and use the context to cancel the query while it is running. For example,
q := db.NewQuery("SELECT id, name FROM users")
err := q.WithContext(ctx).All(&users)
Instead of writing plain SQLs, ozzo-dbx allows you to build SQLs programmatically, which often leads to cleaner,
more secure, and DB-agnostic code. You can build three types of queries: the SELECT queries, the data manipulation
queries, and the schema manipulation queries.
Building a SELECT query starts by calling DB.Select(). You can build different clauses of a SELECT query using
the corresponding query building methods. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
err := db.Select("id", "name").
From("users").
Where(dbx.HashExp{"id": 100}).
One(&user)
The above code will generate and execute the following SQL statement:
SELECT `id`, `name` FROM `users` WHERE `id`={:p0}
Notice how the table and column names are properly quoted according to the currently using database type.
And parameter binding is used to populate the value of p0 in the WHERE clause.
Every SQL keyword has a corresponding query building method. For example, SELECT corresponds to Select(),
FROM corresponds to From(), WHERE corresponds to Where(), and so on. You can chain these method calls
together, just like you would do when writing a plain SQL. Each of these methods returns the query instance
(of type dbx.SelectQuery) that is being built. Once you finish building a query, you may call methods such as
One(), All() to execute the query and populate data into variables. You may also explicitly call Build()
to build the query and turn it into a dbx.Query instance which may allow you to get the SQL statement and do
other interesting work.
ozzo-dbx supports very flexible and powerful query condition building which can be used to build SQL clauses
such as WHERE, HAVING, etc. For example,
// id=100
dbx.NewExp("id={:id}", dbx.Params{"id": 100})
// id=100 AND status=1
dbx.HashExp{"id": 100, "status": 1}
// status=1 OR age>30
dbx.Or(dbx.HashExp{"status": 1}, dbx.NewExp("age>30"))
// name LIKE '%admin%' AND name LIKE '%example%'
dbx.Like("name", "admin", "example")
When building a query condition expression, its parameter values will be populated using parameter binding, which prevents SQL injection from happening. Also if an expression involves column names, they will be properly quoted. The following condition building functions are available:
dbx.NewExp(): creating a condition using the given expression string and binding parameters. For example,
dbx.NewExp("id={:id}", dbx.Params{"id":100}) would create the expression id=100.dbx.HashExp: a map type that represents name-value pairs concatenated by AND operators. For example,
dbx.HashExp{"id":100, "status":1} would create id=100 AND status=1.dbx.Not(): creating a NOT expression by prepending NOT to the given expression.dbx.And(): creating an AND expression by concatenating the given expressions with the AND operators.dbx.Or(): creating an OR expression by concatenating the given expressions with the OR operators.dbx.In(): creating an IN expression for the specified column and the range of values.
For example, dbx.In("age", 30, 40, 50) would create the expression age IN (30, 40, 50).
Note that if the value range is empty, it will generate an expression representing a false value.dbx.NotIn(): creating an NOT IN expression. This is very similar to dbx.In().dbx.Like(): creating a LIKE expression for the specified column and the range of values. For example,
dbx.Like("title", "golang", "framework") would create the expression title LIKE "%golang%" AND title LIKE "%framework%".
You can further customize a LIKE expression by calling Escape() and/or Match() functions of the resulting expression.
Note that if the value range is empty, it will generate an empty expression.dbx.NotLike(): creating a NOT LIKE expression. This is very similar to dbx.Like().dbx.OrLike(): creating a LIKE expression but concatenating different LIKE sub-expressions using OR instead of AND.dbx.OrNotLike(): creating a NOT LIKE expression and concatenating different NOT LIKE sub-expressions using OR instead of AND.dbx.Exists(): creating an EXISTS expression by prepending EXISTS to the given expression.dbx.NotExists(): creating a NOT EXISTS expression by prepending NOT EXISTS to the given expression.dbx.Between(): creating a BETWEEN expression. For example, dbx.Between("age", 30, 40) would create the
expression age BETWEEN 30 AND 40.dbx.NotBetween(): creating a NOT BETWEEN expression. For exampleYou may also create other convenient functions to help building query conditions, as long as the functions return
an object implementing the dbx.Expression interface.
Data manipulation queries are those changing the data in the database, such as INSERT, UPDATE, DELETE statements.
Such queries can be built by calling the corresponding methods of DB. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
// INSERT INTO `users` (`name`, `email`) VALUES ({:p0}, {:p1})
err := db.Insert("users", dbx.Params{
"name": "James",
"email": "james@example.com",
}).Execute()
// UPDATE `users` SET `status`={:p0} WHERE `id`={:p1}
err = db.Update("users", dbx.Params{"status": 1}, dbx.HashExp{"id": 100}).Execute()
// DELETE FROM `users` WHERE `status`={:p0}
err = db.Delete("users", dbx.HashExp{"status": 2}).Execute()
When building data manipulation queries, remember to call Execute() at the end to execute the queries.
Schema manipulation queries are those changing the database schema, such as creating a new table, adding a new column.
These queries can be built by calling the corresponding methods of DB. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
// CREATE TABLE `users` (`id` int primary key, `name` varchar(255))
q := db.CreateTable("users", map[string]string{
"id": "int primary key",
"name": "varchar(255)",
})
err := q.Execute()
Although ozzo-dbx is not an ORM, it does provide a very convenient way to do typical CRUD (Create, Read, Update, Delete) operations without the need of writing plain SQL statements.
To use the CRUD feature, first define a struct type for a table. By default, a struct is associated with a table
whose name is the snake case version of the struct type name. For example, a struct named MyCustomer
corresponds to the table name my_customer. You may explicitly specify the table name for a struct by implementing
the dbx.TableModel interface. For example,
type MyCustomer struct{}
func (c MyCustomer) TableName() string {
return "customer"
}
Note that the TableName method should be defined with a value receiver instead of a pointer receiver.
If the struct has a field named ID or Id, by default the field will be treated as the primary key field.
If you want to use a different field as the primary key, tag it with db:"pk". You may tag multiple fields
for composite primary keys. Note that if you also want to explicitly specify the column name for a primary key field,
you should use the tag format db:"pk,col_name".
You can give a common prefix or suffix to your table names by defining your own table name mapping via
DB.TableMapFunc. For example, the following code prefixes tbl_ to all table names.
db.TableMapper = func(a interface{}) string {
return "tbl_" + GetTableName(a)
}
To create (insert) a new row using a model, call the ModelQuery.Insert() method. For example,
type Customer struct {
ID int
Name string
Email string
Status int
}
db, _ := dbx.Open("mysql", "user:pass@/example")
customer := Customer{
Name: "example",
Email: "test@example.com",
}
// INSERT INTO customer (name, email, status) VALUES ('example', 'test@example.com', 0)
err := db.Model(&customer).Insert()
This will insert a row using the values from all public fields (except the primary key field if it is empty) in the struct. If a primary key field is zero (a integer zero or a nil pointer), it is assumed to be auto-incremental and will be automatically filled with the last insertion ID after a successful insertion.
You can explicitly specify the fields that should be inserted by passing the list of the field names to the Insert() method.
You can also exclude certain fields from being inserted by calling Exclude() before calling Insert(). For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
// insert only Name and Email fields
err := db.Model(&customer).Insert("Name", "Email")
// insert all public fields except Status
err = db.Model(&customer).Exclude("Status").Insert()
// insert only Name
err = db.Model(&customer).Exclude("Status").Insert("Name", "Status")
To read a model by a given primary key value, call SelectQuery.Model().
db, _ := dbx.Open("mysql", "user:pass@/example")
var customer Customer
// SELECT * FROM customer WHERE id=100
err := db.Select().Model(100, &customer)
// SELECT name, email FROM customer WHERE status=1 AND id=100
err = db.Select("name", "email").Where(dbx.HashExp{"status": 1}).Model(100, &customer)
Note that SelectQuery.Model() does not support composite primary keys. You should use SelectQuery.One() in this case.
For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
var orderItem OrderItem
// SELECT * FROM order_item WHERE order_id=100 AND item_id=20
err := db.Select().Where(dbx.HashExp{"order_id": 100, "item_id": 20}).One(&orderItem)
In the above queries, we do not call From() to specify which table to select data from. This is because the select
query automatically sets the table according to the model struct being populated. If the struct implements TableModel,
the value returned by its TableName() method will be used as the table name. Otherwise, the snake case version
of the struct type name will be the table name.
You may also call SelectQuery.All() to read a list of model structs. Similarly, you do not need to call From()
if the table name can be inferred from the model structs.
To update a model, call the ModelQuery.Update() method. Like Insert(), by default, the Update() method will
update all public fields except primary key fields of the model. You can explicitly specify which fields can
be updated and which cannot in the same way as described for the Insert() method. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
// update all public fields of customer
err := db.Model(&customer).Update()
// update only Status
err = db.Model(&customer).Update("Status")
// update all public fields except Status
err = db.Model(&customer).Exclude("Status").Update()
Note that the Update() method assumes that the primary keys are immutable. It uses the primary key value of the model
to look for the row that should be updated. An error will be returned if a model does not have a primary key.
To delete a model, call the ModelQuery.Delete() method. The method deletes the row using the primary key value
specified by the model. If the model does not have a primary key, an error will be returned. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
err := db.Model(&customer).Delete()
To represent a nullable database value, you can use a pointer type. If the pointer is nil, it means the corresponding database value is null.
Another option to represent a database null is to use sql.NullXyz types. For example, if a string column is nullable,
you may use sql.NullString. The NullString.Valid field indicates whether the value is a null or not, and
NullString.String returns the string value when it is not null. Because sql.NulLXyz types do not handle JSON
marshalling, you may use the null package, instead.
Below is an example of handling nulls:
type Customer struct {
ID int
Email string
FirstName *string // use pointer to represent null
LastName sql.NullString // use sql.NullString to represent null
}
Databases vary in quoting table and column names. To allow writing DB-agnostic SQLs, ozzo-dbx introduces a special
syntax in quoting table and column names. A word enclosed within {{ and }} is treated as a table name and will
be quoted according to the particular DB driver. Similarly, a word enclosed within [[ and ]] is treated as a
column name and will be quoted accordingly as well. For example, when working with a MySQL database, the following
query will be properly quoted:
// SELECT * FROM `users` WHERE `status`=1
q := db.NewQuery("SELECT * FROM {{users}} WHERE [[status]]=1")
Note that if a table or column name contains a prefix, it will still be properly quoted. For example, {{public.users}}
will be quoted as "public"."users" for PostgreSQL.
You can use all aforementioned query execution and building methods with transaction. For example,
db, _ := dbx.Open("mysql", "user:pass@/example")
tx, _ := db.Begin()
_, err1 := tx.Insert("users", dbx.Params{
"name": "user1",
}).Execute()
_, err2 := tx.Insert("users", dbx.Params{
"name": "user2",
}).Execute()
if err1 == nil && err2 == nil {
tx.Commit()
} else {
tx.Rollback()
}
You may use DB.Transactional() to simplify your transactional code without explicitly committing or rolling back
transactions. The method will start a transaction and automatically roll back the transaction if the callback
returns an error. Otherwise it will
automatically commit the transaction.
db, _ := dbx.Open("mysql", "user:pass@/example")
err := db.Transactional(func(tx *dbx.Tx) error {
var err error
_, err = tx.Insert("users", dbx.Params{
"name": "user1",
}).Execute()
if err != nil {
return err
}
_, err = tx.Insert("users", dbx.Params{
"name": "user2",
}).Execute()
return err
})
fmt.Println(err)
You can log and instrument DB queries by installing loggers with a DB connection. There are three kinds of loggers you can install:
DB.LogFunc: this is called each time when a SQL statement is queried or executed. The function signature is the
same as that of fmt.Printf, which makes it very easy to use.DB.QueryLogFunc: this is called each time when querying with a SQL statement.DB.ExecLogFunc: this is called when executing a SQL statement.The following example shows how you can make use of these loggers.
import (
"fmt"
"log"
"github.com/go-ozzo/ozzo-dbx"
)
func main() {
db, _ := dbx.Open("mysql", "user:pass@/example")
// simple logging
db.LogFunc = log.Printf
// or you can use the following more flexible logging
db.QueryLogFunc = func(ctx context.Context, t time.Duration, sql string, rows *sql.Rows, err error) {
log.Printf("[%.2fms] Query SQL: %v", float64(t.Milliseconds()), sql))
}
db.ExecLogFunc = func(ctx context.Context, t time.Duration, sql string, result sql.Result, err error) {
log.Printf("[%.2fms] Execute SQL: %v", float64(t.Milliseconds()), sql))
}
// ...
)
While ozzo-dbx provides out-of-box query building support for most major relational databases, its open architecture
allows you to add support for new databases. The effort of adding support for a new database involves:
QueryBuilder interface. You may use BaseQueryBuilder directly or extend it
via composition.Builder interface. You may extend BaseBuilder via composition.init() function to register the new builder in dbx.BuilderFuncMap.FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.