> On 9/18/07, Joel Watson <[EMAIL PROTECTED]> wrote:
> >
> > My initial thought was to create a table with a row for every 
> hobby/interest item.  Then, on the profile table, I was thinking of 
> having a column that would collect a list of comma delimited values 
> from the form, from 1 to the number of the hobby/interest items.  The 
> list would basically match up, sequentially, to the key values of the 
> hobby/interest table.
> >
> > Is there a better way to go about this?
> 
> Depends on if you need to REPORT on that data =)  There are 
> definately
> places where I'll store data like that in a single text field.. and
> other places where I give each piece of data its own field in the
> database.
> 
> You could even put the data into a struct, convert it to a WDDX
> packet, and then store it in a text field in the db.  When you
> retrieve it, it's then very easy to turn it back into a coldfusion
> struct.
> 
> But again.. as long as you don't need to report on or query on that 
> data.
> -- 
> Rick Root
> Check out CFMBB, BlogCFM, ImageCFC, ImapCFC, CFFM, and more at
> www.opensourcecf.
com

Thanks for the response, Rick.

Basically, these values are going to be used to match up vendors with 
users---if the user has selected "hobby 2" and the vendor is looking for users 
like that, there will be a match.  With the list-approach, I was thinking that 
a simple listGetAt(hobbies, hobby2) would get me what I need.

However, I do want to approach this so that there is a measure of flexibility, 
if needed. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion is delivering applications solutions at at top companies 
around the world in government.  Find out how and where now
http://www.adobe.com/cfusion/showcase/index.cfm?event=finder&productID=1522&loc=en_us

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288733
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to