many-to-many

I'm implementing the repository pattern as part of an ASP.NET MVC site. Most examples I've seen of repositories are fairly simple. For example here's a typical abstract repository interface. public interface IRepository<TEntity> { IQueryable<TEntity> All(); TEntity FindBy(int id); TEntity FindBy(Expression<Func<TEntity, bool>> expression); IQueryable<TEntity> FilterBy(Expression<Func<TEntity, bool>> expression); bool Add(TEntity entity); bool Update(TEntity entity); bool Delete(TEntity entity): } It's clear to me how you would use a repository like this to add, update, delete, or get entities

An example Many-to-Many through relationship in Django: class First(models.Model): seconds = models.ManyToManyField(Second, through='Middle') class Middle(models.Model): first = models.ForeignKey(First) second = models.ForeignKey(Second) class Second(models.Model): Following the documentation on intermediary models , only one model of the pair to be related contains the ManytoManyField , model First in the example above. Is this correct? If so, which model should contain the ManytoManyField field? Are there any differences in using the relationship from either end depending on where the

In my Symfony2 project I have two related entities: Users and Favorites. They have a many-to-many relationship. My application works as follows: In my Twig-page I have an few items with a button 'Add to Favorites'. When you click the button my controller saves the item_id in the Favorites column. But then I want to save the user who added the item to his favorites and here my application fails. The User and the favorite exist but the joincolumn between Users and Favorites remains empty. I also don't receive any kind of errors. Here is my code: Entity Users class Users implements

Let's say we have an entity that contains a list of users on the server, and we want to expose this as rest. What is the proper way to do it? My first guess is something like this: /entity/1/user/5 We can use PUT for updates and DELETE for deletes? Is this right? I went to wikipedia where it talks about rest, and their view of it is that everything is only 1 level deep. So maybe they want you to use PUT/POST and give the entire JSON graph and update the entire thing all at once? Your example is a perfectly valid approach. However in many cases a User can exist outside of the context of just