Doug and Team,

I have a iterator problem. I use an iterator to create dynamic navigation 
system. It looks like the query caching is not working correctly, because of 
the new items that are being added and therefore the cached query is breaking.

Is there a way on certain iterators to force the query to NOT cache?

Thanks... (the error is below).

- JS


ERROR:

An error occured at 11/26/2007 10:03:07 PM CST 

ERROR MESSAGE:

The element at position 5 cannot be found. 

ERROR DETAILS:



ERROR EXTENDED INFO:

NONE PROVIDED 

TAX CONTEXT:

C:\Inetpub\wwwroot\_Frameworks\Reactor_v428\query\query.cfc (46)
C:\Inetpub\wwwroot\_Frameworks\Reactor_v428\project\Symphony\Queries\mssql_2B11BC46A28BC3365AA9F9080EC0853E.cfm
 (1)
C:\Inetpub\wwwroot\_Frameworks\Reactor_v428\base\abstractGateway.cfc (90)
C:\Inetpub\wwwroot\_Frameworks\Reactor_v428\iterator\iterator.cfc (480)
C:\Inetpub\wwwroot\_Frameworks\Reactor_v428\iterator\iterator.cfc (632)
C:\Inetpub\wwwroot\_SYMPHONY_CORE\model\data\Record\PageDefinitionRecord.cfc 
(134)
C:\Inetpub\wwwroot\_SYMPHONY_CORE\model\data\Record\PageDefinitionRecord.cfc 
(71)
C:\Inetpub\wwwroot\_CAM-Public\views\dsp\dspSecondaryBody.cfm (7)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\view\ViewRenderer.cfm
 (4)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\view\ViewRenderer.cfc
 (25)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\framework\ModelGlue.cfc
 (435)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\framework\ModelGlue.cfc
 (325)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\framework\ModelGlue.cfc
 (265)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\unity\ModelGlue.cfm 
(108)
C:\Inetpub\wwwroot\_Frameworks\ModelGlue_Unity_v2.0.313\ModelGlue.cfm (4)
C:\Inetpub\wwwroot\_CAM-Public\index.cfm (32)


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reply via email to