> (And I could requote you... but it the thread may debate > what you expressed and what you wanted. I understand you may not want > something more like Benjamine was requesting... but there is > no cause to > create a debate over this. If you don't like an > implementation... build > your own.)
I want to be sure whether I expressed my thoughts obviously. Yes, I sent an approving message saying "you're on the right track" three days ago. However we should change the name of component as e.g. QueryComponent. And QueryComponent is a different thing from QueryIterator component. When we keep in the scope of iteration task, there is no problem with the implementation differences. Here's my grouped comments for each component: QueryIterator: - does stateful iteration, so it contains isFirst, isLast, moveFirst, moveLast, hasNext, moveNext, hasPrevious, movePrevious and getColumn/getRow (and maybe setPosition and getPosition) methods, nothing more. - getColumnList, getColumnType, getRecordCount and other metadata and data manipulation methods should not be in QueryIterator component. - there may be different implementations of this iterator component but all of them should only do iteration. If they do other things this means they are not iterator components they are different things which do iteration also. QueryComponent: - This component is a different thing from iterator component. It is an alternative of CF's query object. - This component may does stateful and stateless iteration and it may contain all functions related to the queries. - I think, however we should find good reasons to develop this component since CF already has functionalities which are really necessary. So what are the reasons for this component? IMHO there is no real-world reason to develop this component (in last three days I thought and discovered this). Murat. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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/cfcdev@cfczone.org
