and sometimes you get sick of using a hammer to build a fence and wish you had a nailgun to get the damn job finished in time (the "5%" factor I mentioned).
leaving aside for the moment that this thread was origionally dealing with Application.cfc (and my opinion that while it's welcomed it's still only catch-up)... ... and continue with CFQUERY Vs ADO/ADO.NET (until someone get's sick of it and brings us all back on topic)... IMHO there's nothing wrong with adding a recordset cursor in the language. Sheesh, it's been there for the last 2 years that I know of (and is probably used by CFLOOP query="XXX") - undocumented (ie: unauthorised)! my points are 1) these CFMX recordset cursors have been undocumented for so long. I find it hard to believe that it hasn't been added to the wishlist already or that MACR thought it unworthy to include unprompted. 2) if there's baggage about using a new tool like an old one then bypass the whole issue and use java for the data access (as some CF people have already done). Don't want to use CFDOCUMENT for PDF? use IText and call the java classes directly from CF. Want an asyncronous gateway without CF7Ent? look at *java.lang.Thread*. I mean, why use CF at all? and the answer to that, of course, is productivity! 3) Emulating ADO (classic) features is old hat anyway. complex problems require more (last week I needed more for a PITA report). Have a good look at how ADO.NET works. It's not perfect. Some of it is a bit bloated and OTT (typical MS). But it has some great ideas there - things that take 10 minutes to do that CF would take half a day to try and acomplish. Eg: have a look at datasets + datatables + datarelations (the modern version of ADO classic's "Shape" feature). Try doing that in CF in 6 lines of code. It's like an allan key (hex-head wrench/tool). You'd never use it every day but's perfect for the right job. and what's wrong with wanting a few of them in your toolbox? any opinions? dissagreements? cheers barry.b -----Original Message----- From: [EMAIL PROTECTED] on behalf of John Farrar Sent: Thu 2/24/2005 12:05 AM To: [email protected] Cc: Subject: Re: [CFCDev] Using application.cfc to modify the request stream CF isn't ASP or DAO based data. Therefore you are talking about tying to use a hammer like a nail gun... or a router like a drill. They are similar, and that covers the difference. It is difficult as you said to program CF like ASP. It's also difficult to program ASP like CF. Your argument lacks relevance. They do it different. You just have brain baggage trying to use the new tool like an old tool you learned to use. There is no real weakness... and there is a way to do what you are asking. (It's just not built in as a extra set of functions. Put a request in to the wish list... they might be able to add a recordset pointer if you wanted... but you could also create a CFC to handle this. That would work better than a custom tag IMHO.) John Farrar ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
<<winmail.dat>>
