I've got a design choice to make, but I'm concerned of the performance implications as well. I've got another eComm site coming up and I need to customize the models/products a bit. The difference from the last is the amount of characteristics each product might have. Things like color/design/material (and a slew of others) exist in this project. My first thought was to make a join on dmCategory and just make it branch specific for each characteristic. This would mean just the dmCategory object creation. My problem is the sheer amount of data that would end up in the category tree. Plus, I'm concerned that the end user would have issues with maintenance on it.
My other thought is each characteristic gets its own object. The problem here is than I have somthing like 15-20 objects to define just ONE product. Sometimes there'd be more, depending on the amount of models attached to a product. It's not a big deal when viewing the product detail, but I'm not sure what kind of load time searches are going to bring back with that much object manipulation. I'm looking for suggestions and/or stories of others that may have gone down the same forks in the road ;). -- Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog twitter.com/ophbalance -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
