> -Original Message-
> From: John Monfort [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 30, 2001 5:08 PM
> To: Mark Roedel
> Cc: [EMAIL PROTECTED]
> Subject: RE: [PHP] Best Practice-HTML In Database
>
>
> Yes, I will need to provide searching capabi
Yes, I will need to provide searching capabilities.
Basically, I'm creating an online referencing system with a db backend.
A user will be able to search for a manual, and/or browse to a
particular section of the manual.
It's similar to the online PHP manual...at least, in concept
> -Original Message-
> From: John Monfort [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 29, 2001 10:40 PM
> To: [EMAIL PROTECTED]
> Subject: [PHP] Best Practice-HTML In Database
>
>
> Hello everyone,
>
> I'm curious. Which is the better practice?
>
> 1) Insert the HTML page (...HTML
Using an URL to point to an HTML page or file is
better.
Inserting the HTML page in the database would cause:
a) more database requests and thus heavy load on the
database
b) large amount traffic between the database server
and the web server
At my previous company we even ended up removing the
If you ever need to update the HTML, option 2 will be a lot easier.
Mick
On Sun, 29 Apr 2001, John Monfort wrote:
>
> Hello everyone,
>
> I'm curious. Which is the better practice?
>1) Insert the HTML page (...HTML code) in the database ?
>
>or
>
>2) Insert a URL in the dat
5 matches
Mail list logo