The Case Against Coding for Portability - DATABASES ARE DIFFERENT
February 12, 2004[From ColdFusion Developer's Journal]
Conventional wisdom dictates that code, all code, be written with portability in mind. After all, you wouldn't want to have to revisit and rewrite code when moving between platforms or environments, would you? And while I do believe that coding for portability is a good thing in general, I also believe that when it comes to databases and SQL, coding for portability is a very bad thing indeed.
Putting It in Context In the past few weeks I was involved in two long e-mail threads:
The article continues at http://www.sys-con.com/coldfusion/article.cfm?id=705