Closed john-kelly closed 6 years ago
The notion of a transformer: http://emberjs.com/api/data/classes/DS.Transform.html
brings up an interesting point. to what extent should one's schema transform that data received from the server?
Query.map seems to work in all cases for general transformation needs. I think most of the data transformation should live in maps, but I'm not yet convinced :)
https://www.reddit.com/r/haskell/comments/66ih1l/selda_a_monadic_database_edsl/ https://github.com/carlosdagos/haskell-sql-edsl-demo https://khibino.github.io/haskell-relational-record/
AND ALL OF THE OTHER HASKELL THINGS! (haskelldb, opaleye, esquelto, and others that i forgot)
This gives me the feeling that making relationships and fields separate things is a good idea. http://docs.sqlalchemy.org/en/rel_1_1/orm/tutorial.html#building-a-relationship
1.) Schema represents from json -> to elm type 2.) Schema represents just from json
I think 2 (based on convo with elm-graphql guy)
Based on this conversation, how should things be named? https://en.wikipedia.org/wiki/Relation_(database) https://docs.djangoproject.com/en/1.10/ref/models/fields/ http://www.django-rest-framework.org/api-guide/schemas/ https://hexdocs.pm/ecto/Ecto.Schema.html http://graphql.org/learn/schema/