At 3:19 PM +0200 22/4/02, Maxim Maletsky \(PHPBeginner.com\) wrote:
>PostgreSQL is the best choice on my opinion. mySQL might fail on a large
>DB.
I'd love to see an example or detailed anecdote of MySQL failing on a
large DB. I keep seeing comments saying MySQL is not robust, but in my
experien
Chief Developer
www.PHPBeginner.com // where PHP Begins
-Original Message-
From: Richard Archer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: Re: [PHP] Database and files
At 11:25 AM +0100 22/4/02, Danny Shepherd wrote:
>If you get
Hi all,
Another bug bites the dust...
Thank you so much for your responses...
As for the DB/filesystem issue, we need to be able to easily replicate this
at some time to another server as the system may easily become a
distributed intranet system. We made the decision to use a database as th
- Original Message -
From: "Richard Archer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 22, 2002 11:40 AM
Subject: Re: [PHP] Database and files
> At 11:25 AM +0100 22/4/02, Danny Shepherd wrote:
>
> >If you get multiple requests for
At 11:25 AM +0100 22/4/02, Danny Shepherd wrote:
>If you get multiple requests for files, expect the db to fall over very
>quickly - what's wrong with storing them on the filesystem and having a list
>of them in the db?
If your DB falls over, get a better one. You wouldn't do this with
Access, b
At 12:19 PM +0200 22/4/02, David Russell wrote:
>Header("Header("Content-Disposition: attachment; filename=\"File65.doc\"" );
That's not right. Must be a typo.
Make sure there is no output before the header function calls.
I use:
header("Content-type: application/octet-stream; name=\"$fname\"
- Original Message -
From: "David Russell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 22, 2002 11:19 AM
Subject: [PHP] Database and files
> I have a database. It receives from my users files - which could be word
> documents, Adobe PDF files, text docs, anything...
>
7 matches
Mail list logo
