It really does come down to preferences, but I would typically do something like this:
qry_getrecords.cfm - takes a query to select records. I would use conditional logic to add "Where id in (#attributes.ids#), unless the length of attributes.ids is 0. dsp_list.cfm - displays a drill down list of all records returned in the qry. dsp_detail.cfm - displays detailed information about an individual record. in the index.cfm file, I'd create 2 fuseactions. One called listrecords, the other called showdetail. Either one calls the same query, except that the showdetail has a parameter to pass. Dave ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 24, 2002 9:00 AM Subject: How atomic does each fuse need be? > Hi all, > > I'm doing something very basic here, and I thought it would serve as a > good place to make sure I'm on the right track. It may just come down > to a matter of preference, but I'd just liek to double check. > > I need to display listing of records and then the individual records > detail. > > I was thinking about having two fuses: qry_records & dsp_records, and > just using conditional logic in both the query fuse and the display fuse > to determine both what query to run and which format to display. > > Is this wrong? I mean, I can certainly break it down into 2 query fuses > and two display fuses, but is this necessary? I know this is a simple > example, but it will serve to better understand just how atomic each > fuse needs to be. > > Thanks! > > ==^================================================================ 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 ==^================================================================
