Having a table with 10,000 is no big deal. That's what databases are
for: to efficiently organize data. Are you familiar with indexing?
If not, go do a little research in that direction to figure out how
to make your queries fast. Having a table with 10,000 rows is far
better than having 10,000 tables. You should be able do a
complicated fetch on a properly indexed table with 10,000 rows
literally within a blink of an eye.
Mark
On Jun 22, 2007, at 2:06 PM, .::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.
But if it's really okay to have one table for all users then I
might as well stick with WebObjects then.
I think I'll try Chuck's and Jacky's solutions first.
_______________________________________________
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]
