1 controller = 1 model VS. 1 controller = multiple model

I do this for authentication, because the tables are all related, and most don't need their own model.

Ah, like moving hashes to separate table, away from your normal firstname, lastname, etc table?

I have been pondering for some time if I should implement that on our stuff, because really, hashes are only used once, during login, and kinda bloat user table for any other case.

Glad to see someone else thinks it's a good idea too.