On 22.06.2007, at 12:06, .::welemski::. wrote:
It's like this. I'm creating a webapplications for work groups. Each user that is registered in the database can have a table on their own. So each user can register a member or a user can register to be a member of that user.Each main user can have a domain of their own and each member can have a blog of their own.It would be nice to separate them because one my friend told me that it would be inefficient to have all of them on one table. Imagine a table with 1000 or 10000 or more records that would be inefficient for them for fetching. He also added that it'll have impact on time in terms of fetching.
This should not be inefficient on any decent database. You try to optimize something when there is absolutely no need to optimize. Build a useful database model, add the correct indexes, qualify on limiting values (like the user or the group) together with others and you're done.
Follow the most basic rule in software development: make it work, make it right, make it fast. Don't optimize things that don't need optimization. And don't trust your friends. ;-)
cug _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
