I don't understand, you wish to join project, and rewrite the core ?
No, I'm researching possible options to give a client what they need in the most expeditious and efficient manner as possible.
The project will easily exceed 100,000 items. The project involves updating a music industry catalog and related information.
So while the structure of your component may be normalized, my question had to do with the users data. With every entry that is made on the site, we need to minimize the redundancy(normalization). For example for album data, if users would have to enter the artists name and info with each album submitted, the db is not normalized, because the same information is listed several times. In addition if different types of user data is stored in basically one table, its not normalized. Without mentioning any names, they are quite a few components that function this way.
Thanks for your intelligent response George.
For the peanut gallery... ha-ha very funny. Hmmm lets see, spend 2-4 hours installing a component, figuring out how it works to determine if it does what you need it to do, or spend 10 min. asking the developer? :roll: