rick_db VS goqu

I forgot to add that most of my "custom" implementations are also open-source, to avoid repeating the same boilerplate over and over at different places. Its not "pythonic", and it is at varying degrees of maturity, and honestly, they are mostly for internal use in my projects (documentation is incomplete, interfaces may change, etc), but if you want have a look:

https://github.com/oddbit-project/rick_db - postgresql query builder & object mapper - it is built around the concept of pure data objects (no indirect references do open resources) that can represent application data between layers; It also features a forward-only migration manager;

https://github.com/oddbit-project/rick - plumbing, validation & assorted logic - provides service locators, registries, containers (including dependency injection); validators, forms & request validation (with support for laravel-style validation chains), and a bunch of other stuff;

https://github.com/oddbit-project/pokie - flask-based web meta-framework, focused on REST api design, that brings components from the other two projects into an modular applicational framework;

That is basically the description of an object mapper, with all the guarantees of an object mapper :). It seems if you actually use the query builder as such, no guarantees exist.

I'm pretty picky regarding query builders and ORM's, to the extent of having written several of them over the years, in different languages (both dynamic and strong typed, unfortunately closed-source). I'm a strong advocate of schema-first design, and usually a query builder will allow you to design your queries explicitly, but having some internal behaviors (such as string concatenation, identifier quoting and automatic in-order separation of parameters and values to be bound) taken care of. As good examples of this, I'd mention golang's goqu (https://github.com/doug-martin/goqu) and - to some extent - C# SqlKata (https://sqlkata.com/). Following my frustrations with Python ORMs, I built my own toy project, sort-of-in-beta, called rickdb (https://github.com/oddbit-project/rick_db).

For SQL, I'd probably go with goqu http://doug-martin.github.io/goqu/

I use goqu (https://github.com/doug-martin/goqu)

SQL Builders (think squirrel or goqu)

I've been looking for a package that allows me to build Postgres DDL statements in Golang. I'm currently using Goqu (https://github.com/doug-martin/goqu) for building statements and it works great, however it does not have support for building schemas. Basic things like creating tables, creating indexes. A great one in JavaScript can be found here: (https://knexjs.org/guide/schema-builder.html#essentials) I have been unable to find anything in Go, does anyone know of any packages like this?

Then use something like https://github.com/doug-martin/goqu to build the SQL.

Try this

We've been using goqu and it's super nice! although there are a ton of other query builders that could better fit your use-case.

If the statement is too dynamic to use query parameters I'd ideally use a dynamic query builder rather than concatenating strings. Goqu is a lib like that but I haven't yet used it personally https://github.com/doug-martin/goqu