http://stackoverflow.com/search?q=nullif+%5Bsql-server%5D
1500+ questions on NULLIF on SO...
http://stackoverflow.com/search?q=nullif+%5Bsql-server%5D
1500+ questions on NULLIF on SO...
Should IP, JSON or geolocation data types (to name a few from Postgres) be ignored for portability if you are targeting Postgres during development and have no plans to port your app to another database? I suspect the answer relies on the specifics of your situation, and how likely it is you actually will need to target another DB.
In some ways, non-standard functions are easier, because you could probably recreate most of those from scratch if you had to.
Such a wire protocol standard would likely evolve a lot faster than the stick-in-the-mud that is the SQL standard, because the "shimability" of such proxies would allow app developers to start confidently using new DBMS features much earlier, the same way frontend developers use new Javascript APIs rather fearlessly given the existence of a rich system of polyfills in NPM. And then DBMS vendors—like browser vendors—would be driven to add said features to their own systems much more quickly, since now their developer-base would use the polyfills—but be annoyed by them as they did so—and the vendor could ameliorate that annoyance by shipping the feature. (Rather than the current world, where the best-practice is "just don't use anybody's custom extensions", so developers don't tend to know what they're missing to get annoyed.)
http://stackoverflow.com/search?q=nullif+%5Bsql-server%5D+is...
results in 337 answers. This is still a large number though because NULLIF is a ridiculously simple function to use. Base upon a small sample, these questions appear to be due to either misordered expressions or poor grasp of order of operations that happen to involve NULLIF.
Is like use Java, and think is wrong to use any code apart of IF, WHILE, ARRAY and ASSIGNMENT because the extra is non-standard across languages.
You have a powerfull RDBMS.
NOT USE THAT POWER IS IDIOTIC.
Instead of down-vote, think hard why do you have that belief and if truly the reason apply TO EVERYONE ELSE.
---
In the other hand, why is instead "ok" to use a NoSql database? EVERYTHING is non-standard, in contrast with sql.
Who, thinking rationally, will deny to use the full redis features just because is "non-standard"?