> > | b.. Ability to run queries against existing query > > result sets (CFSQL). > > > > I don't understand the need for that. Couldn't you just run > > another query? Or is it some sort of performance issue thing > > since the query is in memory? > > Since the query is stored in memory (I assume resident only > while the page is processing) you would be running your sub queries > against memory. This would be a big time performance boost over > running traditional queries because of the difference between > the speed of memory access vs. db access. Not to be a wet blanket, but this isn't necessarily so. The problem here is that CF doesn't currently execute SQL statements. All it does is pass those as strings to the database, which executes them and returns the appropriate recordsets. Now the people who make the databases spend an awful lot of time (and money) optimizing query execution. They take advantage of indexes, alternate possible paths, bind parameters, and other stuff to make SQL run very fast. When Allaire puts in an SQL analyzer, it's unlikely that it'll match the best efforts of Oracle and Microsoft in SQL execution efficiency. To have a chance at making this work, Allaire may have to incorporate a complete in-memory database, in my opinion, which will make the base product more complex and potentially more fragile. Just a thought. I could be wrong. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
