Definitely feeling the full force of Framework Love now.
Oh what's that, creating an object is now a complex operation requiring multiple queries and some cross-table validation? Haha fuck you nothing you've used so far works any more, enjoy your everything being full of suck asshole
@command_tab Not python, but Ecto (in Elixir) has similar facilities... However, in explicitly need to not hide the association table, because in this relation the association table carries additional data.
It's all possible, I just... need to grok how to plumb it through the layers of form helpers and data validators and all that.
@danderson Oh man, mapping tables with additional important columns are, in fact, full of suck. On one hand, the normalization accurately captures the data, but on the other hand, <confused math lady gif>
@command_tab Yup. I essentially spent all day doing the various two-choices memes between correct normalized entity graph vs. denormalized pile of poo, and mostly concluding that computers were a mistake :)
Okay, okay. It seems the root of my woes here is partly that the stock scaffolding uses a single form for creating and editing, whereas I'm about to make those flows diverge real hard. If I first peel apart the create and edit states, I think the complexity collapses back into something more manageable.
The other part of the problem is that I've been deferring getting to grips with Ecto's query DSL and the full force of changeset management, and... yeah, this is the point where I have to actually figure my shit out.
Add comment