Adding timestamps to users_roles is not respected

[saizai]

1. add t.timestamps to the users_roles table in migration
2. add a new role
3. notice that the role got timestamps but the user_role didn't (so you don't e.g. know when the user got that role)

[koshuang]

+1

It would be better if timestamp could work.

[wldcordeiro]

You wouldn't know when a user got a role, only when that role is created, just FYI.

[koshuang]

Is it a restriction or a philosophy of design ?

I am just thinking it can be tracked if we have the timestamp.

For example, assume we have two roles: user, presenter. A user can apply for a presenter. So we want to know when he or she applies.

[wldcordeiro]

The timestamp would be on the Role table which would track the creation of the Role. Since the users_roles table is created as a HABTM it can't store a timestamp, if the table could instead be created as a has_many through then it would be possible to store the timestamp, the only problem being backwards compatability. So to fix this #318 would need to be fixed as well. We do take pull requests from the community. :)