Should Html Formatting Be In A Database?

So recently, I had a go at it with the db guy at work over this.  In the end, nothing changed short-term but I made my point and things will change long-term.  I have decided to share this with you for discussion:

At work, we are deploying some new code next week and as always, the testers are going full blast.  On one of the pages, we display an error message based on certain conditions.  Let's say the text says, "hello world".  In FF, the text shows up  correctly but in IE, it shows up as "hello worldd (note the extra "d").  The defect was assigned to me.

First thing I did was look at the file.  All it had was <%=error %> (We use JSP at work).  So I determine that it is java-based.  I get with the software guy but it isn't in there.  We then go to the db guy.  This is where I saw wonders.  It had html tags, surrounding the actual error text.  I then pasted the code in my text editor and validated it, only to find out that it was missing a closing SPAN tag.  I tell the db guy to insert the SPAN tag to which he responds (most likely cos he doesn't want to "suffer" to insert it in his script), "add it after the error print statement.  I got pissed.  I was like, "since you are the one adding html formatting in the db, what's to say that tomorrow you won't screw up again, making my SPAN tag useless.? Besides, during my code review, most likely, the question will be asked, "why do you have <%=error%></span>?  Why do you even have html and css in your db script?  That is my domain".

As I said, he didn't want to do anything short-term but long-term, it was decided that yes, it doesn't make sense for the db guy to be doing my job, so to speak.

So the question (in case I am missing something), "other than for when you are developing a cms app, does it make sense to add html and css formatting into a table column?  If no, why? If yes, why and give examples"

Let's discuss.

It shouldn't. Not even the slightest "non belonging" slash  . Defeats the goal of separating code from layout. But is damn-as-hell-convenient when done the first time. I've fumed over this in similar scenarios, CMSes in particular. At the very least, the top level elements should not be included in the Database.

@yawa, now i understand your question.

depends on the situation at hand, if u have a site with a backend that enables admin to create html pages, then u have no option but to save your full html pages in your DB. but if they wont be creating html pages, why save html in the DB?

as per the formatting issue, i think your organization needs to google more, removing a "d" programmatically MAY break your code when another upgrade comes out for your platform (u know what i mean)

No.  Because it simply does not make any sense. Presentation level work should be done by those that are well suited to do so.

1. Coding standards need to be established for every project in order to avoid this kind of uncertainty, where was your project manager?



2.  html? YES if the data to be marked up is strictly presentation data;  for example populating a drop down list (<select>) from the database with option groups.
     Css in a database NO!!!!!!!!!

3.  NO if the data is not presentation data; for example client details.

^^@hostmot

Exellent contribution to the thread. Offtopic, besides using table-less format for your website, Commenting in your mother's tongue really has me inspired this early in the morning.

@webmonk

Its just the comments that you saw. You didnt notice the id attributes of the structural divs. It was done by our support guy. Thats our Bill Cosby.

@yawa-ti-de
You don't need to recommend that kinda coder to your company, Microsoft or Google would have snapped him up.

No.

I believe all your formatting should be handled outside the db. This seperates content from design.

To start with, i might get entagled in a web just like you did and start editing my db when trying to fix it. You db is just meant to store information and display when and where needed. Your css decides how it should look like.

just my thoughts.   

I'm personally working out a small CMS application and I noticed that it is not really a nice option saving HTML tags to the DB because most times it conflicts with the HTML formatting on the web pages. Though I still think you could add them into posts body for formatting the texts. I said this based on my coding anyway. I used a simple textarea without any WYSIWYG editor integrated. But I'll try integrate one and see if there will be any difference.

Please i need html and web design tutor.