Storing text with HTML mark up is in most times considered as "bad coding practices".
On first hand it may look tempting, if you pull data out of de DB you only have to declare the CSS classes and voila, done....
But what if you want to present your data in a different way? For instance, you want to change a table into an unordered list? If you only have twenty records or so its not a problem, but what if you have thousands of records?
If you want to add HTML markup to your data you must do that if, and only if, you are very certain this data will only be used as text, but after several years it might happen that no one remembers how to define the css for those chunks of data...
And what if your database has grown to thousands and thousand of records with HTML code and after several years certain tags become deprecated? Or even worse, new standards with better presentation features have emerged, then you are tight down to old fashioned standards...
Second of all, if you have data that can be presented in tables it looks like you have to store that in a seperate record and relate those records with key columns. That's the power of a relational database!
Keep in mind that if you store data using HTML tags to seperate values you are mixing the DAL (Data Acces Layer) with the presentation layer.
Believe me, it's bad coding practice not to tease us pour web developers, no it's to help us create flexible maintainable web applications.
-----
Why use decimal values for currency, because data itself must describe what it is.
CSS is pure presentation layer...
Greets...
