On 22.06.2007, at 12:58, Jacky Gagnon wrote:
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.
To make that absolutely clear:
As long as you're not going to fetch ALL rows (which doesn't make
sense for you anyway), every decent database system is able to handle
millions or even billions of rows. For billions you should be
prepared to do some optimization and to get some decent hardware ... ;-)
I have a small application that seems to do about the same stuff your
app is going to do with about 500k rows in the biggest table. And the
performance is quite good. And now the interesting part: the box is
blue&white PowerMac G3 400MHz with 512MB RAM, and two 18GB SCSI
harddrives. It handles web server, database server and the (one)
Webobjects application. So, you really shouldn't worry too much...
What I want to say: The worst you can do is trying to find a
complicated and ugly way around an issue that doesn't exist. If your
friend tells you, it's a problem for him, tell him to use his
database properly or use a database at all.
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]
