> It is important to separate user interface issues from database > issues. There is no need (from what I understand) to have both name > and gl code in the database as if you (the programmer) knows one then > you are able to determine the other. If you want both on the UI then > that is no problem, just work the other one out when you need to > display it.
OKay okay so basically instead of categorizing them by their name as a string just categorize them by their gl_code and the gl_code is what will be saved in the db and I can just work out displaying the expense type name on the UI. The only thing is the employee that is inputing their expense doesnt always know the gl_code or if ever because to them its meaningless (to the endpoint person its important) So maybe When they choose what kind of expense it is make it a dropdown list with the Expense type name and the gl_code and then it'll just save the gl_code. This would be a belongs_to has_many relationship between expenses and gl_codes PS thanks for helping thus far Colin. I'm the only developer here at my work and have no one to bounce ideas off of or thoughts so this has been helpful -- 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/114c368483cc82819e8e36119a3ed614%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
