[I was wondering what happened to my previous attempt at this email, then realized I sent it to [email protected]. Here goes nothin'...]
I'm sure that this has come up before, so feel free to reply with links or search term suggestions... For the people who keep a good deal of business logic in the DB, this question is probably a no-brainer, but for those of you who keep their business logic in their application model (IBO users, users of a Singleton-helper-class-per-hairy-BO, etc.): How do you handle a requirement to be able to search on or sort on a calculated field? For instance, OrderableProduct.getPrice() might have (and does, in my project-in-planning) have all kinds of dependencies and calculation gymnastics. How could you possibly have both: 1. Performance (how to avoid a general query--a recordset of *all* rows that's then altered/filtered in the app--a seemingly obvious performance problem) 2. DRY business logic Maybe this is impossible, and an instance where (copied or moved) business logic necessarily ends up in the database. So, how's this done? Blech, Jamie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
