Filtering, groups and events: model and saving

Regarding issue https://github.com/getsentry/sentry/issues/1267
Created the eventfiltertagvalue model, and created migration for it.
Saving the new data to database is done in event_manager.py

This is the first draft with just "It runs" tests done to it. 

What do you think about the saving part. My knowledge of djangos querysets is limited and so i don't know how efficient my code really is.

Is there a reason for explicitly naming the table something different from the model name?