I am currently putting together a Seaside website for my radio show. I am trying to figure out how to model the "has and belongs to many" relationships.��
Each episode can have many tracks, each of these tracks can belong to several episodes.
I want to be able to present a listing of which episodes each track appears in, and a listing of tracks for each episode.
The approach I have seen on this is to create an intermediary object and store a set of ids on this, but this seems a little clunky, and it seems like there would be a clean way to do this.
This is how you'd model many-to-many relationships in relational databases.��
If that is where your data is stored, you may be forced to this.
If you are keeping your design purely in the object-oriented domain,��
although I've not enough experience with it to know if its the best way.
Or you might try relation slots.�� ��Check out SlotExampleMovieAndPersonTest.
which I'd guess is still useful even if I read somewhere it was a bit out of date.
cheers -ben����