When you say "one giant query" that sounds a lot more complex than a simple inner join. If that is the case I would put this off until you have some dead time (ha! he says).
One SQL statement does make for more elegant code and it is a faster. But as suggested above - as long as the maintenance cost is the same - the end user experience is all that matters. It is all about what is best (least expensive - usually over the long run) for the business owner. If there are many developers that maintain the app, and they have different SQL skill levels, it can be better to use more than one query. Really complex SQL can be hard to follow if it isn't commented which makes life rough on people without those skills. There are too many programmers that expect everyone to be at their level and have a screw you attitide toward follow on developers. While they might be very bright people, their actions are not in the best interest of the business owner. Programmers as a group need to shift their thinking from 'code as art' or 'code as ego' to 'coding to solve problems and help people'. OK - I'm off my soapbox now. www.CTek-Media.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [EMAIL PROTECTED] For more options, visit http://groups.google.com/group/houcfug?hl=en -~----------~----~----~----~------~----~------~--~---
