---- Russ Michaels <[email protected]> wrote: <snip> > It is also easier from a self containment and portability point of view to > keep SQL within the application. Stored Procs written for MSSQL clearly wont > run on MySQL.
I hear this sometime and wonder how many times you have to port something to another DBMS. I have never had to do so. I guess I have had to assure that code ran properly when we got a new version of MS-SQL Server though. I wondered about it since DBMS portability is given as a reason to code certain ways. I usually have the database transactions in specific modules so I can go back to the code easily. I don't abstract the SQL so it works in a SQL ISO standard. That seems limiting and not worth the trouble. Is it common for systems to be ported between different DBMSs? -- LinkedIn: http://www.linkedin.com/pub/roger-austin/8/a4/60 Twitter: http://twitter.com/RogerTheGeek Blog: http://rogerthegeek.wordpress.com/ http://www.misshunt.com/ Home of the Clean/Dirty Magnet ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:337494 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
