> I expect the CFMX6.1 box to be slower in DB access because
> of the java translation layers

You may be pleasantly surprised, then. There don't appear to be a whole lot
of additional translation layers; you don't use ODBC or OLEDB at all with
the "pure Java" JDBC drivers from MM/DataDirect or MS.

> NOTE: One reason also, why most people do not like to use
> cfstoredproc is the lack of caching options. The only reason
> why I would use cfstoredproc, is to handle multiple returned
> datasets.

If you're using MS SQL Server, you can call stored procedures from within
CFQUERY and still use CACHEDWITHIN/CACHEDAFTER. Conversely, if you were
using passthrough SQL and CFQUERYPARAM within a CFQUERY, you can't cache
that either. In general, I'd recommend that you use Session, Application or
Server variables to cache recordsets, instead of using
CACHEDWITHIN/CACHEDAFTER.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to