RE: cfmodule a query call

[Michael Rahmn]

John-   what's FuseQ? I'm real curious, 'cause weve been building a circuit app to run all query calls through to eliminate duplicate files as well as variablize the hay out of all selects, updates and inserts. Looks something like this:   <cfmodue              template="#request.wRoot##request.self#"              fuseaction="q.Select"              dataSource="#request.DSN#"              table="roster"        fields="field1,field2">   or   <cfmodue        template="#request.wRoot##request.self#"        fuseaction="q.Update"        table="tableName"        field1="#variables.blah#"        field2="#variables.blah#"        field3="#variables.blah#"        where="id=#variables.tableID#"   >   the circuit app then grabs the right include which has all the logic to do its thing and in case of selects, return caller.queryRecordset.   -mike rahmn -----Original Message----- From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 9:53 PM To: [EMAIL PROTECTED] Subject: RE: cfmodule a query call You could use FuseQ to handle that and your required use of CFMODULE would decrease. There will be a few articles up on the techspedition.com site about FuseQ during the weekend. (Actually I think we have the MVC articles up there but not the intro to FuseQ one)   -----Original Message----- From: Tom Schreck [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 2:22 PM To: [EMAIL PROTECTED] Subject: cfmodule a query call 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?   Thanks -   Tom Schreck 817-252-4900 [EMAIL PROTECTED]   I have not failed.  I've found 10,000 ways that won't work.   - Thomas Edison   ==^================================================================ This email was sent to: [EMAIL PROTECTED] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV70o5 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 ==^================================================================ ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================