Thanks a lot. The only problem is that I already have Cars context and although it could look similar to you, the data stored there are very different - that is the reason for a different table name.
Could you try that again if you know this information? I mean only the shell commands themselves - you don’t have to write the description of each element.
Also, for cars_from_alternative_universe and men_women_children tables, please. Thank you in advance.
Hi!
The only problem is that I already have Cars context
Could you try that again if you know this information?
Sure! Alright, so you want a different context name? You can give it a context name of your choice, you don’t need to use the same one:
mix phx.gen.context KalkatfyodorAwesomeContextname CarAll cars_all model:string price:string
It’s good to play with the generators, they are very powerful.
Also, for
cars_from_alternative_universeandmen_women_childrentables
Given what I shared above, what have you tried so far? Please share and we can discuss further.
mix phx.gen.context KalkatfyodorAwesomeContextname CarAll cars_all model:string price:string
That’s not what I want to find out. I am fully aware of the possibility of having a name for context that doesn’t resemble the schema and/or table name.
Can you try that with cars_from_alternative_universe and men_women_children tables? If it’s not possible, then OK, I will try to ask on SQL forums or something, but I would like to see how you (and others) reason and how you try make things as consistent and logical as possible - especially when it comes to Phoenix/Ecto conventions.
That’s not what I want to find out. I am fully aware of the possibility of having a name for context that doesn’t resemble the schema and/or table name.
Can you try that with
cars_from_alternative_universeandmen_women_childrentables? If it’s not possible, then OK, I will try to ask on SQL forums or something
I think this is beyond me at this time. Please go ahead and ask in the SQL forums. After you do, do you mind reporting back? I’d love to know how you solved this when you do. Thanks!
OK, thank you anyway. Also, it would be interesting to hear Chris or some other Phoenix heavyweights on this topic and how would they solve this task 
Alright I’ll bite. So first off, let’s just establish that one single context can have more than one schema inside of it. So if you already have
mix phx.gen.context Cars Car car....
Now your application needs to deal with cars that come from an alternate universe, which have enough different details that you want to keep them in a different table, but they’re similar enough to our dimensional cars that you still want to use the Cars module to manage them. You could then do
mix phx.gen.context Cars CarFromAlternativeUniverse cars_from_alternative_universe...
OK, so what about your other example? Let’s say you now need to track who bought your cars, you could do
mix phx.gen.context Purchaser ManWomanChild men_women_children...
Now it’s also possible to have two schemas in two different contexts refer to the same database table. Let’s say our car application also wants to know, in addition to who purchased the car, who is the riders in the car for any given trip. We could create a Riders context to handle all the logic around tracking riders, and then do
mix phx.gen.context Riders ManWomanChild men_women_children...
This now creates a new context which has a schema which refers to the same table that we created before. You can have some of the fields on the table exposed in the Purchaser schema, and some in the Riders schema. Your schema doesn’t need to have all of the fields that the table has. You can also safely refer to the same database fields from both the Riders and Purchaser schema.
Hope this helps! I’m still not certain on what exactly database structure you had in mind, so I’m not sure where cars_all would fit in, but hopefully you can see how the schema, context, and database all relate from these examples.
Thank you. A nice explanation. Especially with the two contexts for the same table. I didn’t know about that.