Technically you can do both. If it just for you you may want to keep it fast and make a config file that you edit every year. If you want to sell it, follow the peoplesoft approach: everything in the database
You can combine both by using db().select(....,cache=(cache.ram,3600)) On Nov 4, 12:43 pm, "Wes James" <[EMAIL PROTECTED]> wrote: > I am creating a scholarship application with web2py. I wondering how > to code or implement these items. > > I have several dropdown lists: > > Expected Graduation: > Fall 2009 or Spring 2010 > Fall 2010 or Spring 2011 > Fall 2011 or Spring 2012 > Fall 2012 or Spring 2013 > > Ethnicity: > American Indian > Asian > Black or African American > .... > etc. > > Gender: > Female > Male > > How many overall credits at end of Spring 2008 > 1-29 (Freshman) > 30-59 (Sophomore) > ... > etc. > > Should I put these in to a database or just make lists out of them > that can be edited each year (as years change)? I'm guessing for the > Expected grad year, I could implement some kind of python code that > does now+1, now+2, now+3, etc... for the years. > > thx, > > -wj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
