> -----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 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.
>
>
> So, in the long run, which will be more beneficial:
> 1) HTML code inside the db fields?
> or
> 2) HTML URL inside the field?
Well, I know I'm going against most of the rest of the responses you've
gotten, but if you think you're going to need to do databasey things
with the material, it makes sense to me to put it in a database.
Having said that, I do agree with a lot of what the other posters have
said regarding things like the impact on ease of maintenance, waste of
storage space, etc.
If it were me, I think I'd be looking for a way to only store the actual
text in the database, with some PHP scripting to apply whatever
formatting/template is needed to generate the page you want to present.
---
Mark Roedel ([EMAIL PROTECTED]) || "There cannot be a crisis next week.
Systems Programmer / WebMaster || My schedule is already full."
LeTourneau University || -- Henry Kissinger
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
