Logo

dev-resources.site

for different kinds of informations.

New PostgreSQL ORM for Golang: Enterprise

Published at
12/20/2024
Categories
go
postgressql
webdev
database
Author
samet_burgazoglu
Categories
4 categories in total
go
open
postgressql
open
webdev
open
database
open
Author
16 person written this
samet_burgazoglu
open
New PostgreSQL ORM for Golang: Enterprise

Why we need a new ORM?

There are actually a few good ORMs available, but they just didn't meet my needs. So what did I want?

  • High performance
  • Schema as code
  • Statically typed and generated api code
  • Less generated file
  • Simple and Functional
  • Easy RawSQL usage
  • Single db hit filter when join relation

At the moment I can't say enterprise do well all of the things I mentioned. But it aims to do so.

So let's look what enterprise do.

High Performance

You can see the benchmark source code here.
https://github.com/MrSametBurgazoglu/go-orm-benchmarks/tree/enterprise

Benchmark Results

As you can see enterprise is very well at performance.

Schema as code

Like many others enterprise generate db models from your code.
Here is a little example

// db_models/account.go
package db_models

import (
    "github.com/MrSametBurgazoglu/enterprise/models"
    "github.com/google/uuid"
)

func Account() *models.Table {
    idField := models.UUIDField("ID").DefaultFunc(uuid.New)

    tb := &models.Table{
        Fields: []models.FieldI{
            idField,
            models.StringField("Name"),
            models.StringField("Surname"),
            models.UUIDField("TestID").SetNillable(),
        },
        Relations: []*models.Relation{
            models.ManyToOne(TestName, idField.DBName, "test_id"),
            models.ManyToMany(GroupName, "account_id", "group_id", "id", AccountGroupName),
        },
    }

    tb.SetTableName(AccountName)
    tb.SetIDField(idField)

    return tb
}
Enter fullscreen mode Exit fullscreen mode
// generate/generate.go
package main

import (
    "example/db_models"
    "github.com/MrSametBurgazoglu/enterprise/generate"
)

func main() {
    generate.Models(
        db_models.Test(),
        db_models.Account(),
        db_models.Group(),
    )
}
Enter fullscreen mode Exit fullscreen mode

When you execute the script above it will create a package named models and put two file for each table named model.go and model_predicates.go . And there will be a client.go for using db.

Statically typed and generated api code

After auto-generate models you can create and get models.


import "/your/project/models" // your auto-generated models package

func main() {
    db, err := models.NewDB(dbUrl)
    if err != nil {
        panic(err)
    }

    ctx := context.Background()
    account := models.NewAccount(ctx, db)
    account.SetName("name")
    account.SetSurname("surname")
    err = account.Create()//row added to table
    if err != nil {
        log.Fatal(err)
    }
}
Enter fullscreen mode Exit fullscreen mode

import "/your/project/models" // your auto-generated models package

func main() {
    db, err := models.NewDB(dbUrl)
    if err != nil {
        panic(err)
    }

    ctx := context.Background()
    account := models.NewAccount(ctx, db)
    account.Where(account.IsIDEqual(uuid.New()))
    err = account.Get()//row variables set to account struct
    if err != nil {
        log.Fatal(err)
    }
}
Enter fullscreen mode Exit fullscreen mode

Less generated file

Like I said before enterprise generate 2 file for each table and one client file who uses all of them. It handles most cases in own package this way you will have more clean structure.

Simple and Functional

Enterprise aims simple and fuctional interaction with db fields. For this, fields have helper functions.

Let's say you have a nillable uuid named face_id on table and you represent it with *uuid. Enterprise will generate a helper function to set it with string. That way you don't need to get pointer of that variable.

func (t *Account) SetFaceIDValue(v uuid.UUID)
Enter fullscreen mode Exit fullscreen mode

If you have a uuid field it will create a parser helper.

func (t *Account) ParseFaceID(v string) error
Enter fullscreen mode Exit fullscreen mode

For some value types it will have IN clause.

func (t *Account) FaceIDIN(v ...uuid.UUID) bool
func (t *Account) FaceIDNotIN(v ...uuid.UUID) bool
Enter fullscreen mode Exit fullscreen mode

For time.Time it will create these helper functions.

func (t *Account) FormatCreatedAt(v string) string
func (t *Account) ParseCreatedAt(layout, value string) error
Enter fullscreen mode Exit fullscreen mode

Easy RawSQL Usage

Enterprise can create complex queries but need for RawSQL always will be. Because of that you can use models.IDatabase to interact with pgx. We have plans to scan raw sql result to your db models or custom structs you create with relation if need.

Single db hit filter when join relation

One of the most important features that separates Enterprise from others is can join relations and filter them with single query.

One example is like this. Let's get a student's wrong answered test questions where test score higher than 80.

s := models.NewStudent(ctx, db)
s.Where(s.IsIDEqual(studentID))
s.WithTestList(func(testList *models.TestList) {
    testList.Where(
        testList.IsPointGreaterThan(80),
    )
    testList.Order(models.CreatedAtField)
    testList.WithQuestionList(func(questionList *models.QuestionList){
            questionList.Where(
                questionList.IsAnswerEqual(False),
            )
    })
})
err = s.Get()//row variables set to model and its relations struct.
if err != nil {
   log.Fatal(err)
}
Enter fullscreen mode Exit fullscreen mode

For repository: https://github.com/MrSametBurgazoglu/enterprise
For documentation: https://mrsametburgazoglu.github.io/enterprise_docs/

postgressql Article's
30 articles in total
Favicon
GraphDB for CMDB
Favicon
Not able to connect to PostgreSQL server on Fedora
Favicon
Master Test Data Generation With dbForge Studio for PostgreSQL
Favicon
Exploring the Power of Full-Stack Development with Next.js and Prisma
Favicon
Bringing PostgreSQL Query Issues to Light with Insightful Visuals
Favicon
POSTGRESQL - ÍNDICE GIN NA PRÁTICA
Favicon
Reading PostgreSQL Query Plans Brought to a New Level
Favicon
Understanding PostgreSQL Isolation Levels
Favicon
How to Activate and Enable the PostgreSQL Service on Your Kali Linux System
Favicon
Mastering charts and database visualization with ChartDB
Favicon
The Best Ways to Connect to a PostgreSQL Database
Favicon
Hey, welcome to my blog
Favicon
How to Create a Database and Always Connect to It in PostgreSQL Without Needing Superuser Access
Favicon
03. ரிலேஷனல் டேட்டாபேஸ் மாடல் என்றால் என்ன? What is Relational Database Model ? (RDBMS)
Favicon
04. தரவு ஒருங்கிணைவு (Data Integrity)
Favicon
02. DBMS என்றால் என்ன? What is a DBMS?
Favicon
How To Use Materialized Views
Favicon
PostgreSQL Secrets You Wish You Knew Earlier
Favicon
Reading Parallel Plans Correctly
Favicon
New PostgreSQL ORM for Golang: Enterprise
Favicon
Migrate 🪳Coackroach DB into Postgres🐘
Favicon
💡 Database Development: It’s Not Just About Querying!
Favicon
Building Real-Time Data Pipelines with Debezium and Kafka: A Practical Guide
Favicon
01. தரவுத்தளம் எவ்வாறு உருவானது, அதன் தேவை என்ன? How did the database come about, What is its need?
Favicon
Data inconsistency in AWS Amazon Aurora Postgres solved with Local Write Forwarding?
Favicon
PostgreSQL vs. MySQL
Favicon
How To Handle Custom S/DQL Queries On Different Database Engine with DoctrineExpression
Favicon
Deploying PostgreSQL on Kubernetes: 2024 Guide
Favicon
Step-by-Step Guide to Installing PostgreSQL on Arch Linux
Favicon
Remedy for Poor-Performing SQL Queries

Featured ones: