Embedding html code in stored procedures

Question

We seem to have a few developers here who think creating stored procedures that spit out HTML or Javascript code is a legitimate thing to do. In my mind this is the ultimate abuse of the separation of concerns model. Is doing something like this people have often seen people doing?

Answer 1

Yucko. There are a few issues:

• Can't 'skin' the app - move to a totally new presentation like Flex, desktop forms, etc.
• You prevent graphic designers or UI experts from working in an environment that's productive for them.
• If you mix your HTML storage (some in templates, some in the db, some in app code), it's absolutely awful to track down UI issues.
• No IDE DOM/layout validation
• You can't preview or prototype without running the db.