> >My understanding from what we talked about last night Nolan is that you > >want to do as Marc suggested and separate the SQL from the CFML to > further > >simplfy the CFML. This would be a reason for doing this. > > > Hey Rick, > > Last night we spoke about running all queries in the application file as > opposed to a per request basis. This way the queries are always > available to be referenced. I realize that using stored procedures only > increases the server performance with certain scenarios. > > In the same way that all queries are run in the application file, could > you 'run' all your <cfstoredproc> statements in the application file as > well, and reference the results throughout the site? > > Maybe I'm just thinking up crazy things. Does this even make sense?
Obviously you could run all your CFQUERY or CFSTOREDPROC in the Application.cfm but wouldn't that be a huge overhead since you'll likely not use all those recordsets on every request? What you could do is have an initialistaion script which stores all the recodsets into Application variables (This might use up a lot of memory if you have huge recordsets) and then implement and update of those varibales upon changes in the database and rather than calling CFQUERY or CFSTOREDPROC to refernce the needed recordset just use those stored in the Application scope variables. Also, if you plan on using alot of Application variables, which requires CFLOCK for reading, you might consider having a template that copies the most frequently used App variables (like your column list) to the REQUEST scope. Good luck, Marc - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "Marc Campeau" <[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)
