-
Notifications
You must be signed in to change notification settings - Fork 2
SQL Connection & Go ORM #12
Comments
This could change to func RegisterUser(db *SqlxBlah) error {
return func (w http.ResponseWriter, h *http.Request) {
//old code
}
}
|
@adelowo yeah I definitely agree that DI was the way to go, I'll look into this approach! For the example you posted, would you need to change it to this? func RegisterUser(db *SqlxBlah, w http.ResponseWriter, h *http.Request) error {
return func (w http.ResponseWriter, h *http.Request) {
//old code
}
} How do you feel about the ORM? I started off with that just to get something up |
|
I should be able to help out on a couple things though |
@adelowo sorry I just wasn't too sure what you were saying but I think I see it now for the Yeah if you could show an example without the ORM I'd really appreciate it! And feel free to contribute to any part 😄 |
Can i pull a fork of this showing that ? or how do you want me to "show the example" ? |
Yeah a fork, a gist, or whatever works 😁 |
A fork it shall be... Should get that done in a couple hours |
Ok, i found out i already have something like this.. You might want to look into it Database => https://github.com/adelowo/reblog/tree/master/models (plus mocks) |
I agree with the DI approach. This article does a good job showing a few approach. |
Yep I've switch it using DI! |
I'm quite new to using SQL with Go, so if anyone has any opinion or design proposals post them here!
As of now:
main
package (Maybe switch to dependency injection to pass it around?)gorm
as our ORM, maybe we don't need an ORM andsqlx
would be enough?The text was updated successfully, but these errors were encountered: