4 ms·
Not including an ORM layer does not decrease "value" of this framework, because you can attach such lib on your own. In Go the you are very flexible to set up a
by piotrkubisa 10y ago
Not including an ORM layer does not decrease "value" of this framework, because you can attach such lib on your own. In Go the you are very flexible to set up a "a place where data will be stored/queried" - there is fabulous database/sql (or additional layers like lib/pq [1]) which is great for many use cases; also orm-like solutions like gocraft/dbr [2]; oh, I also should mention Gorm [3] or Bolt [4]. Setting them up is really easy in any Go web frameworks because (almost) all database modules rely on abstraction from stdlib.
[1] https://github.com/lib/pq https://github.com/lib/pq
[2] https://github.com/gocraft/dbr https://github.com/gocraft/dbr
[3] https://github.com/jinzhu/gorm https://github.com/jinzhu/gorm
[4] https://github.com/boltdb/bolt https://github.com/boltdb/bolt
- rattray 10y agoThat's true; the same could be said for many other parts of the stack, including several features that were included, like TypeScript compilation. Given that interacting with a database is at least as common a webdev task as, say, i18n, I thought it was worth noting that this framework does not have a db solution of choice.
- ptman 10y agoIsn't lib/pq more like a driver that's used through database/sql than an additional layer ?
- piotrkubisa 10y agoIndeed. Thank you for pointing this out.