>> ...and I'm just a grumpy bastard when it comes down to it... > > You too eh?! Phew thought I was the only one :-)
hey, i'm president of the grumpy club ;o) i've seen early versions of byron's code, and it wasn't bad back then, so after several years of CF, he will have learned even more in particular, the order of his advice is good -- > 1. How clean and efficient your code is. For scalability etc... > 2. How robust your database is. For scalability etc... number 1 includes putting stuff into stored procs, but even if you cannot, you can still do plenty to get efficient code for example, never do a SELECT inside a CFLOOP or CFOUTPUT -- seen that way too many times you can get a lot of mileage out of number 1 before you need to upsize from access and mysql like byron says, okay for light-weight apps haven't had a chance to actually testdrive postgresql myself, but i can vouch for the robustness of its sql rudy http://rudy.ca/ - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "rudy" <[EMAIL PROTECTED]> To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
