MarthinL
MarthinL
> I've managed to get rid of `dynamic` for constructing association queries. Will work on docs next. As always, testing is very welcome! Hey @soundmonster, yeah, me too. I've arrived...
> Hi @MarthinL, > > To test his branch you can point your Ecto and Ecto SQL dependencies at his branches in `mix.exs` and then update your deps: > >...
> You can still have foreign keys while maintaining a unique ID for the association itself. > I suspect we're talking cross-purposes with regards to my use case. If it...
> For your deps issue it looks like it's asking you to put `override: true` so it overrides those nested deps. I solved it another way: I cloned phoenix_ecto from...
Hi @soundmonster and @josevalim, So far so good, I have set up this PR's code on my machine and it seems to be running as expected. I'm not sure I...
> I'm sure your use case would benefit from this a lot and would be a good test. I'd just hate to see your app be limited if this is...
> I'm sure your use case would benefit from this a lot and would be a good test. I'd just hate to see your app be limited if this is...
### I'm stuck on syntax and semantics and need help. My little exploratory project came along just fine as long as I stick to simple `belongs_to :owner, Owner` and `has_many...
> Hi @soundmonster and @josevalim, > > So far so good, ... **except, not really.** When I couldn't seem to get the more complex variants of associations working I went...
Apologies. When the consequences of multiple mount/3 calls (on different servers) became significant to me I didn't make the connection to this issue and if I correctly follow along with...