As part of a ticket open to give users the preference of changing the default pagination setting in the system search, I've decided to create a new table which will store all user preferences. At the moment the only user preferences (email and display name) are in the main tg_user table.
As the potential preferences could grow quite large I thought we should move all that out into a new user preferences table which has a FK relationship to the tg_user table.
Should we just add all the future preferences (and I can see there being a lot) into the current tg_user table?
Cheers Raymond
Raymond Mancy wrote:
As part of a ticket open to give users the preference of changing the default pagination setting in the system search, I've decided to create a new table which will store all user preferences. At the moment the only user preferences (email and display name) are in the main tg_user table.
As the potential preferences could grow quite large I thought we should move all that out into a new user preferences table which has a FK relationship to the tg_user table.
Should we just add all the future preferences (and I can see there being a lot) into the current tg_user table?
Cheers Raymond
Raymond, I believe there is a BZ on this already. But one thing that would be good is to have a unique password. What I mean by that if I Take a machine or reserve a a system. I would like the default password to be unique. I do not want the default set by the system.
Thanks, Jeff
On Mon, Apr 12, 2010 at 11:30:43PM -0400, Raymond Mancy wrote:
As part of a ticket open to give users the preference of changing the default pagination setting in the system search, I've decided to create a new table which will store all user preferences. At the moment the only user preferences (email and display name) are in the main tg_user table.
As the potential preferences could grow quite large I thought we should move all that out into a new user preferences table which has a FK relationship to the tg_user table.
you could code up a user preferences object that would initially be hardcoded with all the values. Then over time you can allow users to set them via a UI. But then you don't have to go through all the places in the code and convert set_pagination(rows=50) since you've already future proofed yourself with set_pagination(rows=User.Prefs.pagination_rows).
Should we just add all the future preferences (and I can see there being a lot) into the current tg_user table?
Cheers Raymond _______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/beaker-devel
beaker-devel@lists.fedorahosted.org