Re: Database Question!
| From: | The Captain | Date: | Tue, 05 Sep 2000 16:54:48 +0000 |
| Subject: | Re: Database Question! | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-15326@lists.php.net to get a copy of this message | ||
on 9/5/00 12:49 PM, Lars Holm Nielsen at lars@rck.dk wrote:
> Hi,
>
> I don't know if PHP is able to handle this data. I would guess that it would
> depend more on the database that your using than PHP. As long as you doesn't
> need to display all 40 millions rows at once.
> But if PHP is not working I would recommend using Java servlets (look at
> Tomcat on http://jakarta.apache.org/tomcat/index.html or
> Enhydra at
> http://www.enhydra.org), while they definitely should be able
> to handle it.
Using java servlets would be a good idea if you are using oracle. The MySQL
and Postgres java libraries are slow and a big pain.
PHP can definitly handle this amount of data. You'll never return 40
million records to a webpage, so the amount of data in the database is not
even a factor. All php (or any back-end language you use) does is submit a
query, and wait for the database to return the data.
The main question you need to ask yourself is what kind of database you want
to use. I would stronly suggest oracle. It's fast and very reliable.
However, I wouldn't overlook MySQL here. If the tables are constructed
correctly, you shouldn't have problems doing queries with properly formatted
"where" clauses.
As long as you have a DBA with a good head on their shoulders, you should be
fine. A webpage will probably get 50 records at max i would imagine, if
anything more than that... you should definitly paginate. I wouldn't want
to sit and wait for a query result page that's 200K.
Good Luck,
Capt