xo

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

Xo Alternatives

Similar projects and alternatives to xo

  • sqlc

    xo VS sqlc

    Generate type-safe code from SQL

  • SQLBoiler

    xo VS SQLBoiler

    Generate a Go ORM tailored to your database schema.

  • InfluxDB

    Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.

  • igor

    xo VS igor

    igor is an abstraction layer for PostgreSQL with a gorm like syntax.

  • bud

    xo VS bud

    The Full-Stack Web Framework for Go

  • tempdb

    xo VS tempdb

    Key-value store for temporary items :memo:

  • prometheus

    xo VS prometheus

    The Prometheus monitoring system and time series database.

  • BTrDB

    xo VS BTrDB

    Berkeley Tree Database (BTrDB) server

  • SonarQube

    Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

  • dat

    xo VS dat

    Go Postgres Data Access Toolkit (by mgutz)

  • ent

    xo VS ent

    An entity framework for Go

  • geocache

    xo VS geocache

    Geocache is an in-memory cache that is suitable for geolocation based applications.

  • go

    xo VS go

    The Go programming language

  • cheerio

    xo VS cheerio

    Fast, flexible, and lean implementation of core jQuery designed specifically for the server.

  • sqlx

    xo VS sqlx

    general purpose extensions to golang's database/sql

  • pggen

    xo VS pggen

    Generate type-safe Go for any Postgres query. If Postgres can run the query, pggen can generate code for it.

  • sqlgen

    xo VS sqlgen

    Go tool for generating sql scanners, sql statements and other helper functions

  • pggen

    xo VS pggen

    A database first code generator focused on postgres (by opendoor)

  • jet

    xo VS jet

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

  • go-mysql

    xo VS go-mysql

    a powerful mysql toolset with Go

  • migrate

    xo VS migrate

    Database migrations. CLI and Golang library.

  • GoSwagger

    xo VS GoSwagger

    Swagger 2.0 implementation for go

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better xo alternative or higher similarity.

xo reviews and mentions

Posts with mentions or reviews of xo. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-03.
  • Matt Mueller: Building Modern Web Applications Faster With Bud
    5 projects | reddit.com/r/golang | 3 Aug 2022
    Sorry for the confusion, we're not generating the database client itself, more like generating an ORM around a database client. The ORM takes these database clients as dependencies. It's very similar to the way XO works with it's multi-database support: https://github.com/xo/xo/tree/master/_examples/northwind
  • What’s your preferred setup to work with SQL DB (without ORM) ?
    10 projects | reddit.com/r/golang | 20 Jul 2022
    i use xo . Reason is i prefer designing schema first and creating golang scaffolding later. Xo takes schema and gives me basic create/update/delete operations by default and i can also generate gocode for any sql queries that i write.
  • Show HN: A Go framework for your projects
    10 projects | news.ycombinator.com | 2 Jul 2022
  • sqlc: Generating go code from sql statements
    4 projects | reddit.com/r/golang | 17 May 2022
    Thanks for sharing your thoughts! I see that it works best with Postgresql. The other commenter mentioned https://github.com/xo/xo for MySql which might work well.
  • Show HN: A Full-Stack Web Framework Written in Go
    18 projects | news.ycombinator.com | 13 May 2022
    Thanks for your comment and question @onionisfruit. Top-notch handle too!

    >> What are your plans for models and persistence?

    I haven't worked out all the details, but it's going to be some blend of https://github.com/xo/xo and https://sqlc.dev/.

    Design goals:

    1. High-level, type-safe "ORM" that's generated from your database schema.

  • We Went All in on Sqlc/Pgx for Postgres and Go
    31 projects | news.ycombinator.com | 8 Sep 2021
    I'm a big fan of the database first code generator approach to talking to an SQL database, so much so that I wrote pggen[1] (not to be confused with pggen[2], as far as I can tell a sqlc fork, which I just recently learned about).

    I'm a really big partisan of this approach, but I think I'd like to play the devil's advocate here and lay out some of the weaknesses of both a database first approach in general and sqlc in particular.

    All database first approaches struggle with SQL metaprogramming when compared with a query builder library or an ORM. For the most part, this isn't an issue. Just writing SQL and using parameters correctly can get you very far, but there are a few times when you really need it. In particular, faceted search and pagination are both most naturally expressed via runtime metaprogramming of the SQL queries that you want to execute.

    Another drawback is poor support from the database for this kind of approach. I only really know how postgres does here, and I'm not sure how well other databases expose their queries. When writing one of these tools you have to resort to tricks like creating temporary views in order infer the argument and return types of a query. This is mostly opaque to the user, but results in weird stuff bubbling up to the API like the tool not being able to infer nullability of arguments and return values well and not being able to support stuff like RETURNING in statements. sqlc is pretty brilliant because it works around this by reimplementing the whole parser and type checker for postgres in go, which is awesome, but also a lot of work to maintain and potentially subtlety wrong.

    A minor drawback is that you have to retrain your users to write `x = ANY($1)` instead of `x IN ?`. Most ORMs and query builders seem to lean on their metaprogramming abilities to auto-convert array arguments in the host language into tuples. This is terrible and makes it really annoying when you want to actually pass an array into a query with an ORM/query builder, but it's the convention that everyone is used to.

    There are some other issues that most of these tools seem to get wrong, but are not impossible in principle to deal with for a database first code generator. The biggest one is correct handling of migrations. Most of these tools, sqlc included, spit out the straight line "obvious" go code that most people would write to scan some data out of a db. They make a struct, then pass each of the field into Scan by reference to get filled in. This works great until you have a query like `SELECT * FROM foos WHERE field = $1` and then run `ALTER TABLE foos ADD COLUMN new_field text`. Now the deployed server is broken and you need to redeploy really fast as soon as you've run migrations. opendoor/pggen handles this, but I'm not aware of other database first code generators that do (though I could definitely have missed one).

    Also the article is missing a few more tools in this space. https://github.com/xo/xo. https://github.com/gnormal/gnorm.

    [1]: https://github.com/opendoor/pggen

    31 projects | news.ycombinator.com | 8 Sep 2021
    I've used https://github.com/xo/xo, extended it with some custom functions for templating, extended the templates themselves, and can now generate CRUD for anything in the database, functions for common select queries based on the indices that exist in the database, field filtering and scanning, updates for subsets of fields including some atomic operations, etc. The sky is the limit honestly. It has allowed me to start with something approximating a statically generated ORM and extend it with any features I want as time goes on. I also write .extra.go files along side the generated .xo.go files to extend the structs that are generated with custom logic and methods to convert data into response formats.

    I like the approach of starting with the database schema and generating code to reflect that. I define my schema in sql files and handle database migrations using https://github.com/golang-migrate/migrate.

    If you take this approach, you can mostly avoid exposing details about the SQL driver being used, and since the driver is mostly used by a few templates, swapping drivers doesn't take much effort.

  • sqlh - The SQL Helper
    3 projects | reddit.com/r/golang | 3 Jun 2021
    Here is an example of the MySQL Django tables generated by GORM https://github.com/xo/xo/tree/master/examples/django/mysql
  • Fighting boilerplate with code generation
    3 projects | dev.to | 10 Apr 2021
  • Code Generation
    10 projects | reddit.com/r/golang | 10 Apr 2021
  • A note from our sponsor - #<SponsorshipServiceOld:0x00007fea593f86d0>
    www.saashub.com | 29 Jan 2023
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic xo repo stats
12
3,305
5.0
18 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com