ORM & Database

[reindert-vetter]

I've thought about that for a long time. But I think we should wait for Generics in Go. I can make all subjects in such a way that gives the same feeling as Laravel, only an ORM needs generics in my opinion.

We could create or accept a query builder. How do we think about that?

[reindert-vetter]

A list of ORMs:
https://github.com/d-tsuji/awesome-go-orms

[rafaelbreno]

I'm used to GORM but I feel a little lack of a well written documentation, looks like I'm reading the code comments instead of the official doc.

Seizing the theme, I'm assigned to the Validation Depth and an ORM would be required for some validation, for example the "unique" keys, would need to verify the table and search for a value(you know). So if there's no rush to implement an ORM would be nice to wait for a Generics so we could think and project calmly an Eloquent-ish package.

[Wulfheart]

I like the idea of waiting.

[bosix]

I use gorm in some of my projects as well and building the query feels really a bit of "laravel-like". Here an example out of one of my projects:

dbc := db.Connection()
courseDataReversed := []db.HistoricCourse{}
dbc.Select("avg(btc) as btc, avg(eth) as eth, avg(ltc) as ltc, avg(bch) as bch, min(id) as id, created_at").
	Table("historic_courses").
	Where("created_at < ?", t.currentTime).
	Where("created_at > ?", t.currentTime.Add((-1)*24*8*time.Hour)).
	Group("created_at_quarter_hour").
	Order("created_at DESC").
	Limit(7*24*4 + 5).
	Find(&courseDataReversed)

The syntax is not that beautiful than it's in laravel but I feel that it's kinda easy to use. I have to admit that @rafaelbreno is right according the documentation. If you have special things to solve (complex subqueries, multiple joins, etc) there are very few examples to work with.

[Wulfheart]

But gorm doesn’t have the simplicity like Eloquent.

[bosix]

@Wulfheart can you give an example of what you mean?

[Wulfheart]

Wait, I mixed it up with something else.
However, I suggest using gorm just until we can implement a solution using generics. But there really needs to be a default solution. Even though this is temporary.

[reindert-vetter]

But there really needs to be a default solution. Even though this is temporary.

Do you want to explain way?

[Wulfheart]

@reindert-vetter just for the sake of simplicity. Same defaults…

[almas1992]

Recommend REL

REL is golang orm-ish database layer for layered architecture. It's testable and comes with it's own test library. REL also features extendable query builder that allows you to write query using builder or plain sql.

[reindert-vetter]

That looks good indeed!

[Wulfheart]

I'd opt for replicating Eloquent in Go with the advent of generics.

[nurmuhammet-ali]

Hello everyone, I really loved the framework, but I don't where it will be better to put database functions, I mean I used to open one database connection in my main.go file then I use it any where, just by passing credential. So, the question is, where it will be better to put my db functions, what I used to do is:

// In main.go
db, err := sql.Open("mysql", dbUsername + ":" + dbPassword + "@/" + dbName)

if err != nil {
 panic(err.Error())
}
defer db.Close()

// then in my other functions/routes, I pass the db, then credentials
createData(db, ...)

// here is the function
func createData(db *sql.DB, ...) {/* ... */}

Thx for attention.

[reindert-vetter]

The syntax will look like this:

INSERT and UPDATE:

result := app.Db().Exec("INSERT INTO employee (first_name, last_name) VALUES ('Reindert','Vetter')")

Or:

result, err := app.Db().ExecE("INSERT INTO employee (first_name, last_name) VALUES ('Reindert','Vetter')")

SELECT:

result := app.Db().Query("SELECT first_name FROM employee;")

Or:

result, err := app.Db().QueryE("SELECT first_name FROM employee;")

In a controller it could look like this:

func Homepage(request inter.Request) inter.Response {
    db := request.App().Db()
    result := db.Query("SELECT first_name FROM employee;")
    if result.Empty() {
        return outcome.Json(errors.New("Not found").Status(http.StatusNotFound))
    }
    return outcome.Html("Name: " + result.Get("0.employee_first_name").String())
}

Or

func Homepage(request inter.Request) inter.Response {
    db := request.App().Db()
    amount := db.Query("SELECT count(*) FROM employee;").First().Int()
    return outcome.Html("Amount: " + amount)
}

I have now only made it for MySQL, but can also make it easy for PostgreSQL.
I will document it. Then it will become clearer how you can get values from the result.

@nurmuhammet-ali Do you already have points for improvement?

[nurmuhammet-ali]

@reindert-vetter Great, it would be perfect, that's exactly what I wanted.

[reindert-vetter]

With arguments:

	result := app.Db().Query(
		"SELECT first_name "+
			"FROM employee "+
			"WHERE first_name = ? "+
			"AND last_name = ?;",
		"Reindert",
		"Vetter",
	)

[reindert-vetter]

@nurmuhammet-ali

I'm ready. The following has been changed in confetti-framework/confetti repo:
PR: #132

I just need to make sure it works in docker. Now I get error:

panic: can't connect with connection mysql: Error 1045: Access denied for user 'app'@'172.19.0.5' (using password: YES)

[lightglitch]

Also have https://entgo.io

[reindert-vetter]

Love it

[Wulfheart]

Generics are available now. Are there any plans?

[emarais-godaddy]

Our team has implemented https://github.com/volatiletech/sqlboiler successfully in some projects before. It's a great way to setup models from your migrations and then use those models those setup database seeds.

It takes away the heavy lifting of creating db boilerplate throughout projects.

[nurmuhammet-ali]

Looks really nice!