Its really not a problem to deal with a table with more than 10 000
records, you just need to index correctly your database and have
enough memory on your database server. You can deal with a table
containing millions of records if you want.
I'm not sure if it will be really faster to have one table for each
user and this design seems to be difficult to maintain. But its just
an opinion and I don't know all your specifications.
Good Luck!
On 07-06-22, at 14: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.
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/jgagnon%
40druide.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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]
