wow, that's a good one. Since you've got a bunch of lists in there, you're best bet is probably to do separate queries and pass in valuelists.
Or another way to do your recordset might be to not pass out lists, but pass out individual records and use the group attribute in cfoutput, like: <cfoutput group="documentid"> Steve Jeff Chastain wrote: > Steve, > > That was the answer I was looking for. I did not know if I had to stick to a query >file only contains a sinlge cfquery statement or if I could do some other things as >long as I sent out the right results. > > If anyone wants to look ... here is the fuseDoc. > > Thanks > Jeff > > -------------------- > > <!--- --> > <fusedoc fuse="qry_getDocumentInfo.cfm" language="ColdFusion" specification="2.0"> > <responsibilities> > I retrieve information about the given document. > </responsibilities> > > <properties> > <history author="david johns" date="2/24/2002" type="create" role="architect"> > </properties> > > <io> > <in> > <string name="dbPath" scope="request" /> > <boolean name="runQuerySims" scope="request" /> > > <string name="documentID" scope="attributes" optional="Yes" /> > </in> > <out> > <recordset name="documentInfo" /> > <string name="documentID" /> > <string name="documentName" /> > <string name="documentFile" /> > <list name="documentAuthors" delimeters="," /> > <list name="documentAuthorEmails" delimeters="," /> > <string name="documentStatus" /> > <list name="approveReviewers" delimeters="," /> > <list name="approveReviewerEmails" delimeters="," /> > <number name="tallyDisapprove" precision="Integer" /> > <list name="disapproveReviewers" delimeters="," /> > <list name="disapproveReviewerEmails" delimeters="," /> > <number name="tallyNA" precision="Integer" /> > <list name="naReviewers" delimeters="," /> > <list name="naReviewerEmails" delimeters="," /> > <number name="tallyNoVote" precision="Integer" /> > <list name="noVoteReviewers" delimeters="," /> > <list name="noVoteReviewerEmails" delimeters="," /> > </recordset> > </out> > </io> > </fusedoc> > ---> > > -------------------- > > ---------- Original Message ---------------------------------- > From: Steve Nelson <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Thu, 28 Mar 2002 11:33:01 -0500 > > >show us your fusedoc, maybe we can figure it out. > > > >Often I'll have a single recordset out that will require multiple SQL statements. >It doesn't matter if it happens in one cfquery or 5, as long as it outputs the >correct data. For that matter you could use the querynew/queryaddrow/querysetcell >functions in CF to make your outputted recordset what you want. > > > >Steve Nelson > > > >Jeff Chastain wrote: > > > >> Supposedly with the FLiP/FuseBox process, an application architect goes through >and "designs" the entire application and in the end has a collection of fusedocs. >Now the database fusedocs get handed off to the DB guy and he/she is supposed to >design the database and all the queries - right? > >> > >> What happens, since the architect does not know anything about the database >design, if the query fusedocs specify something that cannot be accomplished using >just a single query? > >> > >> For example, say I want to retrieve a list of books in a certain genre from a >library, but one of the fields I want returned in the recordset is a the author of >the book. Now, a book can have multiple authors though, so the author field would >actually be a list that would need to be generated from a seperate query. > >> > >> To solve this, can a single query file contain more than one query and some other >CF logic to generate the required result or what happens here? I am running into a >situation like this where I have a set of query fusedocs and a pre-existing database >and there is not a method to use a single query to generate the required results >(unless someone knows how to make a single field in a recordset actually be a comma >seperated list of values from another query?). > >> > >> Thanks > >> Jeff Chastain > >> > > > > > > > ==^================================================================ 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 ==^================================================================
