How do I generate Go code from my MySQL database with sqlingo?

Install sqlingo-gen-mysql via go install, then run it with your database connection string and redirect output to a .go file, as shown in the tutorial. This creates DSL objects based on your schema.

sqlingo vs GORM: which is better for type safety in Go?

sqlingo excels in type safety by generating code from the database for compile-time checks, while GORM relies more on runtime reflection. However, GORM has a larger ecosystem and broader database support.

Can I use sqlingo with PostgreSQL for a production app?

PostgreSQL support is experimental, so it's not recommended for production. Stick to MySQL for stability or consider alternatives if PostgreSQL is essential for your project.

How to handle complex joins and subqueries in sqlingo?

Use the From() method with multiple tables and Where() clauses for joins, and nest Select() queries for subqueries, as demonstrated in the tutorial examples for multi-table queries.

Does sqlingo support database migrations?

No, sqlingo focuses on query building and model generation, not migrations. You'll need separate tools like goose or migrate for schema changes.

How to log SQL queries executed by sqlingo?

Use the interceptor support to implement custom interceptors for logging. Override execution methods to capture and log queries before they run, as mentioned in the features.

Open-Awesome

sqlingo

MITGov0.13.0

A lightweight SQL DSL and ORM for Go that generates code from your database and enables elegant SQL query writing.

GitHub

456 stars26 forks0 contributors

What is sqlingo?

sqlingo is a lightweight SQL DSL and ORM library for Go that generates code from your database schema, allowing developers to write SQL queries in a type-safe, elegant way. It solves the problem of manual synchronization between Go code and database structures while providing compile-time error detection and IDE-friendly features.

Target Audience

Go developers working with SQL databases who want type-safe query building, reduced runtime errors, and better IDE integration without sacrificing SQL expressiveness.

Value Proposition

Developers choose sqlingo because it generates code directly from the database, ensuring models stay synchronized automatically, provides compile-time error checking for SQL queries, and offers an elegant, expressive API with full IDE autocompletion support.

Overview

💥 A lightweight DSL & ORM which helps you to write SQL in Go.

Use Cases

Best For

Building Go applications that require type-safe SQL query construction
Teams wanting automatic synchronization between database schema and Go models
Developers seeking compile-time error detection for SQL queries in Go
Projects needing elegant, expressive SQL DSL with IDE autocompletion
Applications requiring support for MySQL, PostgreSQL, or SQLite databases
Implementing complex SQL queries with subqueries, joins, and transactions in Go

Not Ideal For

Projects using PostgreSQL or SQLite in production, due to experimental support
Teams preferring raw SQL strings for complex queries or stored procedures without abstraction
Applications with rapidly changing database schemas requiring frequent code regeneration
Environments where code generation tools are impractical, such as some serverless or strict CI/CD setups

Pros & Cons

Pros

Auto-Generated Type Safety

Generates Go structs and DSL objects directly from the database schema, eliminating manual synchronization and enabling compile-time checks for SQL queries.

Compile-Time Error Detection

Catches common SQL errors during compilation, reducing runtime failures and improving code reliability, as highlighted in the README.

IDE Integration

Enables autocompletion, field suggestions, and usage tracking in editors, enhancing developer productivity with features demonstrated in the demo GIF.

Full DML and Transaction Support

Supports SELECT, INSERT, UPDATE, DELETE with advanced syntax, subqueries, and transactions, providing a robust API for complex queries.

Cons

Limited Database Support

Only MySQL has stable support; PostgreSQL and SQLite are experimental, which restricts its use in production environments with those databases.

Code Generation Overhead

Requires a separate generation step before building, adding complexity to development workflows and CI/CD pipelines, as shown in the tutorial.

Experimental Non-MySQL Features

Support for PostgreSQL and SQLite is explicitly marked as experimental in the README, implying potential bugs or incomplete functionality.

Frequently Asked Questions

Related Projects

sqlc

Generate type-safe code from SQL

Stars18,061

Forks1,073

Last commit2 days ago

Squirrel

Fluent SQL generation for golang

Stars7,971

Forks516

Last commit2 years ago

Command line tool to generate idiomatic Go code for SQL databases supporting PostgreSQL, MySQL, SQLite, Oracle, and Microsoft SQL Server

Stars3,894

Forks335

Last commit3 months ago

jet

Type safe SQL builder with code generation and automatic query result data mapping

Stars3,769

Forks186

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub