hi tom,
more usual practice would use cfinclude instead of cfmodule to call a
simple qry fuse. the fuse will then live in the same "space" as the
rest of your code, and have access to the same attributes.
you can still put your query fuses in a common place, and use
fusebox.rootpath to find your way there. as for the question about your
strange global attribute scope, i couldn't say, unless you are passinth
the entirte attributes structure, or actually referencing the
caller.attributes structure from the qry fuse.
sorry to be not much help.
leebb
Tom Schreck wrote:
> I originally placed my queries in a central location so I could manage
> them easier then if they were in individual circuits. I would call the
> query via cfmodule. My queries are structured so that if
> IsDefined("Attributes.[variableName]") then include the variable in the
> where clause of the resulting SQL statement. I have a situation where a
> variable is present in the Attributes scope, but it is not being passed
> to the query via the cfmodule, and the query is incorporating the
> variable in the resulting SQL execution anyways. I do not have a
> complete understanding of the process of working down the structure to
> resolve a fuseaction request, but it appears the attributes scope is
> taking on the characteristics of a request scope. I know that's not
> possible, but this is what it seems to be doing. How else can an
> attribute scoped variable be present in a cfmodule call when that
> variable is NOT passed into the cfmodule?
>
> I now place the queries in the circuit and cfmodule them but I use the
> queryname in the template attribute versus calling Index.cfm and passing
> a fuseaction to retrieve the query. This has resulted in the same query
> showing up in multiple circuits, not an ideal situation. I can manage
> it using Visual SourceSafe and sharing the query to multiple circuits so
> I only have to edit it in 1 location. Any suggestions on how to make
> this work better?
>
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
