Just to clarify a little: > Also, in Django one generally only declares the relationship from one "side", unlike Rails where the relationship is declared on bo

Just to clarify a little: > Also, in Django one generally only declares the relationship from one "side", unlike Rails where the relationship is declared on both "sides" (i.e., in Django one simply sets up a ForeignKey on A pointing to B, rather than placing relationship identifiers on both A and B). That's because django will automatically add the reverse of the relation to B, so that you can access A through B. You can disable that functionality optionally though.