> It might be worth using STI but I would start the simple way and see > how it pans out. Refactoring for that sort of change should not be > difficult. > > You might want to consider having expense_type as a table so that you > can add expense types without changing the code. Expense belongs_to > expense_type, but that may or may not be appropriate for your > requirement. > > Colin
Ok so it would be just one form with the options of selecting the type of expense. Then for my requirements I could just use scopes when querying (i.e. "Give me all expenses for this user that are business entertainment.")n essentially right? Cause each expense has a pre defined GL code for it so would you think it would be best to build a Case and When method to preset those before it saves? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c5d10b0d8c7daf7ef56aef78e67c67d6%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
