Macaron: a high productive and modular web framework in Go
11–20 of 52 posts
Re: Macaron: a high productive and modular web framework in Go
#12I quickly looked this over. Does Golang have some hidden ORM like feature that makes complex persistence easy? I spent the last three months working on a storage mechanism that controls all of CRUD at the document level across what is essentially Google Groups (each op is allowed to multiple groups). This is where web work is complex.
Came here to say the same thing. Go won't enter "crud webapp" market until they have a better story on relational db interactions. I'm afraid this is way beyond the current possibilities of the language as it offer barely any meta-programming technics, on purpose.
Re: Macaron: a high productive and modular web framework in Go
#13Earlier quoted context omitted.
Came here to say the same thing. Go won't enter "crud webapp" market until they have a better story on relational db interactions. I'm afraid this is way beyond the current possibilities of the language as it offer barely any meta-programming technics, on purpose.
Did you had a look at sqlx? [1] Granted, it won't generate the queries for you - but parsing into structs works 95% of time without additional mapping for me. Coming from other languages I also found the amount of necessary typing a bit disturbing first. But then you can actually read code instead of orm framework documentation, issue trackers and workarounds. [1] http://jmoiron.github.io/sqlx/
Writing every select for every entity, with all the variations depending on whether you want to inner join with 1-n relationships (and which ones) is really tedious when you've got 30 entities in your model.
Re: Macaron: a high productive and modular web framework in Go
#14I quickly looked this over. Does Golang have some hidden ORM like feature that makes complex persistence easy? I spent the last three months working on a storage mechanism that controls all of CRUD at the document level across what is essentially Google Groups (each op is allowed to multiple groups). This is where web work is complex.
Re: Macaron: a high productive and modular web framework in Go
#15Earlier quoted context omitted.
Came here to say the same thing. Go won't enter "crud webapp" market until they have a better story on relational db interactions. I'm afraid this is way beyond the current possibilities of the language as it offer barely any meta-programming technics, on purpose.
What about https://github.com/go-xorm/xorm ?
Re: Macaron: a high productive and modular web framework in Go
#16Earlier quoted context omitted.
What about https://github.com/go-xorm/xorm ?
Thanks for the link, i didn't know about it. From what i see from the documentation (which looks pretty sparse) it doesn't implement lazy loading or any kind of mapping between SQL relation (1-n , n-n) to and from the go structs, so i guess it's pretty far from any of today's standard.
Re: Macaron: a high productive and modular web framework in Go
#17I quickly looked this over. Does Golang have some hidden ORM like feature that makes complex persistence easy? I spent the last three months working on a storage mechanism that controls all of CRUD at the document level across what is essentially Google Groups (each op is allowed to multiple groups). This is where web work is complex.
There is no ORM like feature anywhere that makes complex persistence easy.
In the past I've had great success with XO, which will generate Go code from an existing DB Schema:
It's really very good!
Re: Macaron: a high productive and modular web framework in Go
#18Does this have hot reloading?
It shouldn't be supported at the router/framework level. Use an external app to monitor changes in a directory and reload the web app.
Re: Macaron: a high productive and modular web framework in Go
#19I read this as Macron at first lol
[1] http://d31f1lobboyy59.cloudfront.net/wp-content/uploads/2014...
Re: Macaron: a high productive and modular web framework in Go
#20I quickly looked this over. Does Golang have some hidden ORM like feature that makes complex persistence easy? I spent the last three months working on a storage mechanism that controls all of CRUD at the document level across what is essentially Google Groups (each op is allowed to multiple groups). This is where web work is complex.