refactor out the dynamic pieces to be replaced by
generated cfc's later.
Best Wishes,Peter
-Original Message-From:
[EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED]] On Behalf Of
Peter BellSent: Thursday, June 29, 2006 9:10 PMTo:
CFCDev@cfczone.org
Subject: RE: [CFCDev] Modeling
-Original Message-
From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On
Behalf Of Peter Bell
Sent: Thursday, June 29, 2006 9:10 PM
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] Modeling a user and its profile
Hi Jeff,
If I understand this right, you have one base application
We use lookup tables. A simplified
version of our ERD is attached.
Basically, you normalize the attributes into
a separate table and then use a one-to-many reference table to map users to
their attributes. For the attached ERD, you can pull a users
attributes with this query:
SELECT
in the database table ... are all attributes expected to fit in a varChar(50)
field?
Thanks
-- Jeff
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roland
CollinsSent: Thursday, June 29, 2006 3:31 PMTo:
CFCDev@cfczone.orgSubject: RE: [CFCDev] Modeling a user and its
profile
We use
] Modeling a
user and its profile
So do you model this in an OO fashion or is this all
database design? I am thinking specifically on the attribute ... is there
different types of attributes (i.e. email, plain text, date, etc.)? Is
there any checking / validation of the attribute? How are you
Title: Message
Hi
Jeff,
If I
understand this right, you have one base application but multiple versions. Each
version can be customized in terms of either selecting from a set of possible
fields and/or creating custom fields. The fields for a given application will
only change if an admin
r BellSent: Thursday, June 29, 2006 9:10 PMTo:
CFCDev@cfczone.orgSubject: RE: [CFCDev] Modeling a user and its
profile
Hi
Jeff,
If I
understand this right, you have one base application but multiple versions.
Each version can be customized in terms of either selecting
