I don’t love this (the default ecto) naming scheme, I do something completely different myself, where I break out into submodules for contexts, schemas, changesets, queries
ityonemo
lc0815
I did that a while back but the torrent of Ecto error messages just got to me, so I took a day off and went back started with the index function on the controller with its main Repo error message and started posting here after failing to get any answers form my friend google that made any sense. I removed all the code I had added to the controller for the other CRUD functionality to make things simple and the posting question smaller and easier to understand and explain.
I also was able to get my react webpages to connect to the controller without any problems until I started hooking up the db functionality, so at least I can hook a web page to the app, that’s something I think.
0
lc0815
yeah, I am having a HUGE problem with the naming/context conventions.i’m also having a problem with breaking changes between different versions for something that can have a big impact on a company’s software selection for its product cycle.
I used to teach SQL, and one of my lectures dealt with names and naming conventions. People don’t realize that this is a very big problem in large applications where you can have 100++ tables with multiple schemas and multiple views where the naming can be a real pain the derriere or somewhere near there… LoL…
anywho: thanks again
thanks again
0
lc0815
PS: what do you do to name your objects, what kind of naming convention do you use. do you any docs on it. would love to see some samples…
0
lc0815
I did a demo using the phx.gen.context and that went well, however, I’m trying to understand the complete process from the bottom up without the sugar coated wrapper generated by the phx.gen.* helper functions.
I also used the phx.gen.schema and the phx.gen.html, but again I’m trying to understand the system from the ground up…
Thanks again.
0
lc0815
ityonemo
there is some trickiness (two or three ways around it) you have to be aware of in order to properly use changesets that are not in the same module as the schema. I honestly don’t really recommend this until you’ve done at least one full project using the Ecto Default. The HyperHypeBeast is optimized for teams of more than about 2-4. Also note that this is just an architecture plan, it still needs to be approved by ben and none of the refactoring has been executed yet (as there are no tests yet, lol)
0
lc0815
well, i’m a bit away form implementing anything like it. I did follow the schemas and found that the module names are singular ie room, versus the schema names which are plural ie: rooms… I need to get a handle on that… which is what @kokolegorille point out to me… I did find some issues with that as well.
moving on…
0
ityonemo
schema names should be singular because an ecto schema creates a struct, so it will generate things that are “objects” and you will want to pass them around like they are single things. Context names should be plural, because they refer to the collections in the tables.
1