Open Source Go Object-Relational Mapping (ORM) Software for Linux

REL is a modern and lightweight ORM for Go that emphasizes testability, flexibility, and composability. It supports a repository pattern and expressive query building with support for advanced SQL features. REL aims to make it easier to write maintainable, testable, and readable database logic in idiomatic Go.

GORM is a powerful, developer-friendly ORM library for Go. It maps Go structs to DB tables, supports relationships, hooks, transactions, eager loading, raw SQL, migrations, and advanced querying with plugins.

XORM is a simple and powerful Object-Relational Mapping (ORM) library for Go. It provides a clean API for interacting with databases, supporting multiple database systems. XORM simplifies database operations by allowing developers to work with Go structs instead of writing raw SQL queries.

Basic types, integers, floats, string, bool, time.Time, net.IP, net.IPNet. All struct fields are nullable by default and zero values (empty string, 0, zero time, empty map or slice, nil ptr) are marshalled as SQL NULL. pg:",notnull" is used to add SQL NOT NULL constraint and pg:",use_zero" to allow Go zero values. sql.NullBool, sql.NullString, sql.NullInt64, sql.NullFloat64 and pg.NullTime. Structs, maps and arrays are marshalled as JSON by default. PostgreSQL multidimensional Arrays using array tag and Array wrapper. Hstore using hstore tag and Hstore wrapper. go-pg supports 2 last Go versions and requires support for Go modules. So make sure to initialize a Go module. ORM supports has one, belongs to, has many, and many to many with composite/multi-column primary keys. ForEach that calls a function for each row returned by the query without loading all rows into the memory.

xorm is a simple and powerful Go language ORM library, through which database operations can be made very easy. This library is a customized and enhanced version based on the original xorm, which provides xorm with ibatis-like configuration files and dynamic SQL support, and supports ActiveRecord operations. This library is based on the customized and enhanced version of the original xorm. Since this customized version has third-party library dependencies (the original version of xorm does not have any third-party library dependencies), the original version of xorm must maintain The third-party library has zero dependencies, so I had to open this Github library separately. The relevant customization functions of this library are developed to solve simpler complex SQL calls and some special business requirements scenarios. The core functions of this customized version of ORM are consistent with the original version, and will be updated with the original version of xorm.

SQLBoiler is a tool to generate a Go ORM tailored to your database schema. It is a "database-first" ORM as opposed to "code-first" (like gorm/gorp). That means you must first create your database schema. Please use something like sql-migrate or some other migration tool to manage this part of the database's life-cycle. While attempting to migrate a legacy Rails database, we realized how much ActiveRecord benefited us in terms of development velocity. Coming over to the Go database/sql package after using ActiveRecord feels extremely repetitive, super long-winded and down-right boring. Being Go veterans we knew the state of ORMs was shaky, and after a quick review we found what our fears confirmed. Most packages out there are code-first, reflect-based and have a very weak story around relationships between models. Work with existing databases: Don't be the tool to define the schema, that's better left to other tools.

LiteSQL is a codegenerator and C++ library that integrates C++ objects tightly to relational database and thus provides an object persistence layer. LiteSQL supports SQLite3, PostgreSQL, MySQL and oracle as backends.

GoRose (go orm), a mini database ORM for golang, which was inspired by the famous PHP framework laravel's eloquent. It will be friendly for PHP developers and python or ruby developers. Currently provides six major database drivers: MySQL, sqlite3, Postgres, Oracle, MySQL. GoRose 2.0 adopts a modular architecture, communicates through the API of the interface, and strictly depends on the lower layer. Each module can be disassembled or even customized to your liking. GoRose provides data object binding (map, struct), and supports string table name and map data return. Provides great flexibility. It is recommended to use data binding to complete the query operation so that the data source type can be controlled.

Bun's goal is to help you write SQL, not to hide it behind awkward constructs. Bun uses database/sql and extends it in a compatible and idiomatic way. Out-of-the-box works with PostgreSQL, MySQL 5.7+, MSSQL, and SQLite. Keep your database schema updated with Go and SQL-based migrations. Provide initial data for your application with YAML fixtures. Modern app skeleton puts everything together and helps you get started. Bun is brought to you by uptrace/uptrace. Uptrace is an open-source APM tool that supports distributed tracing, metrics, and logs. You can use it to monitor applications and set up automatic alerts to receive notifications via email, Slack, Telegram, and others.

go-kallax is a type-safe ORM for Go, designed to work seamlessly with PostgreSQL. It generates Go code from your database schema using model definitions, allowing for clean and performant data access without raw SQL. The library is built with Go idioms in mind and focuses on compile-time safety and ease of use.

A better ORM for Go and database/sql. It uses non-empty interfaces, code generation (go generate), and initialization-time reflection as opposed to interface{}, type system sidestepping, and runtime reflection. It will be kept simple. Now you can say that last invocation is obviously invalid, and that it's not hard to make an ORM to accept both first and second versions. Make sure you are using Go 1.13+, and Go modules support is enabled. Install or update reform package, reform and reform-db commands. Compiler can't check it. Method's signature in godoc will not tell us how to use it. We are essentially working against those tools by sidestepping type system. First version is still invalid, since one would expect Save() method to set record's primary key after INSERT, but this change will be lost due to passing by value.