3 ms·

Features: https://kataras.gitbooks.io/iris/content/features.html https://kataras.gitbooks.io/iris/content/features.html (seems to be missing a data/SQL/ORM lay

by rattray 10y ago

Features: https://kataras.gitbooks.io/iris/content/features.html https://kataras.gitbooks.io/iris/content/features.html (seems to be missing a data/SQL/ORM layer) Usage docs for rest api: https://kataras.gitbooks.io/iris/content/render_rest.html#usage https://kataras.gitbooks.io/iris/content/render_rest.html#us...

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 ago
  That'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 ago
  Isn't lib/pq more like a driver that's used through database/sql than an additional layer ?
  - piotrkubisa 10y ago
    Indeed. Thank you for pointing this out.
znpy 10y ago
Given the state of the art of golang ORMs, I guess this might be a plus. I have tried xorm and gorm (besides database/sql) and while I settled on gorm, they both have some fundamental design flaws: * xorm onInsert/onUpdate hooks are designed the wrong way. Last time I tried, hooks received object instances by value and not by reference, meaning I could not actually update things before hitting the database. * both xorm and gorm have schema-generation capabilities, but have you looked at the schema they generate? Last time I checked, gorm-generated schemas had basically no referential integrity whatsoever, and no foreign key was being generated. But I guess it's only time before a well-done golang ORM shows up.
- benguild 10y ago
  Yeah, with GORM you have to generate the relationships manually.
- nibs 10y ago
  I have had good results with Beego/Beego ORM lately.

by rattray 10y ago

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 ago
That'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 ago
Isn't lib/pq more like a driver that's used through database/sql than an additional layer ?
- piotrkubisa 10y ago
  Indeed. Thank you for pointing this out.

znpy 10y ago

Given the state of the art of golang ORMs, I guess this might be a plus. I have tried xorm and gorm (besides database/sql) and while I settled on gorm, they both have some fundamental design flaws: * xorm onInsert/onUpdate hooks are designed the wrong way. Last time I tried, hooks received object instances by value and not by reference, meaning I could not actually update things before hitting the database. * both xorm and gorm have schema-generation capabilities, but have you looked at the schema they generate? Last time I checked, gorm-generated schemas had basically no referential integrity whatsoever, and no foreign key was being generated. But I guess it's only time before a well-done golang ORM shows up.

benguild 10y ago
Yeah, with GORM you have to generate the relationships manually.
nibs 10y ago
I have had good results with Beego/Beego ORM lately.