And there are other folks who don't know that what you call Oracle syntax is actually ANSI-standard syntax, and that the optional FROM clause in SQL Server is non-standard. In fact, even Access (also microsoft) has a different syntax for the same thing! So beware - if you choose to use this, you can't port your code.
Interesting read. I have to ask though - I have to see any combinations of DBMS' where a straight port of code is simply a matter of cut and paste. Is that really a valid concern?
Yes it does work some of the time, but once you get into "real-life code", every one of the major's seems to have their own intricacies, so you're going to HAVE to re-write some things. Even using "standard code", just because it runs doesn't mean it runs well.
I keep hearing that "what if your RDBMS changed tomorrow" line being thrown around, and just have to take a skeptical approach to that. I've seen ports from one to the other, but they always involve a LOT of re-writing, reoptimizing. If all of them do the SAME thing, using the same code, same optimization tricks, etc... - then they will be no reason for them to be separate products. The cheapest one to license will be the one who takes over, and the others will just fall by the wayside.
Until they act the same, having the same lines of code, well - is worthless IMO. My first priority is efficient and correct, not portable.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?