pculture/mirocommunity — comment on commit 0ef5f9a6ca2629d01386d3f4ae4863cdbce80e1e
File:  line 0
By melinath:

Using table names in the class Meta *is* letting the models get out of sync with the tables. Even though it is clearly stated, and less disruptive than say db_column, it introduces an element of redirection that I would rather not have. I'm pretty sure that the main reason table_name exists is that django doesn't ship with a schema alteration api. Since we're using south, that doesn't really apply to us.

Still, in the interest of not causing a service interruption, I would be fine with using table_name in the short term, until the admin_refactor comes through.