> Why not use dictionary to Map user-level names to database-fields I'm not sure I fully follow what you're suggesting. But it sounds like you're suggesting I move the configuration of field name out of the database and into a Python file using a dictionary to map actual fields to preferred field names. Is this correct?
I can't do this because: * I do not know the user's preference ahead of time * Their preference could change as time goes on * It is unreasonable (in my case) to expect my users to modify python files * These preferences could be different across different installations For this reason, these fields are configured as a sort of "user setting". The user is in complete control. But, once they are set, they should be used everywhere. Cheers, Jon -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADhq2b7%3D_EmMiQtpnLVHUOSPY3wvjBsdiKF%2BbP2WHL%3DhJocvNg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
