It looks fine, Steve, but not much use in my shop's model. We let the db guys
handle the qry files; the Fusedocs tell 'em what we want the fields to be
called so we don't care what the field names in the tables are.
OTOH, if you want it to look the same inside and out...
- Jeff
On 26 Mar 2001, at 19:40, Steve Nelson wrote:
> I just wanted to bring this thread back to the surface... I just added
> this ||Database Objects|| section to my fusedocs and so far it's
> awesome! Made development 'that' much faster. I'm curious to know how
> well it would work in a distributed environment.
>
> Steve
>
> Steve Nelson wrote:
> >
> > Has anyone come up with a good way to describe which tables/store
> > procedures/etc are necessary for a fuse from within a Fusedoc? I'm
> > thinking maybe something as simple as the Fusedoc below (note the
> > "Database Objects" section). I think by knowing which tables the Fuse
> > will be using will be enough information to obtain fields and such by
> > looking in the db.
> >
> > <!---
> > || BEGIN FUSEDOC ||
> >
> > || Properties ||
> > Name: act_updatecoworker.cfm
> > Author: [EMAIL PROTECTED]
> >
> > || Responsibilities ||
> > I will update the roles that a coworker plays in an application
> >
> > || Attributes ||
> > -->attributes.application_id an integer
> > -->attributes.roleslist a comma list
> >
> > || Database Objects ||
> > FuseCAD_Coworkers: a table
> > FuseCAD_Roles: a stored Procedure
> >
> > || END FUSEDOC ||--->
> >
> > P.S. Wait until you see my Fusebox CAD tool. OH BABY! It's 100+
> > Fuseactions of PURE Fusebox Adrenaline!
> >
> > Steve Nelson
> > You're not smart enough!
> > http://www.secretagents.com/training
> > (804) 825-6093
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
