MySQL and the perils of Going Rogue

Since the mid-90’s, I’ve worked fairly extensively with nearly all of the major Relational Database vendors: Oracle, Sybase, SQL Server, DB2, and MySQL. (Even dabbled a bit with Postgres.) I’ve been able to do this without too much trouble because, until fairly recently, the SQL implementations provided by the various vendors were not that different.

Over the past few years though, I’ve noticed more and more deviations from standard SQL coming into play, mostly from MySQL. I’ll admit I do not follow developments in the ANSI spec process, so some of these may be SQL-92 standards, but I suspect most are not. For example, take “INSERT IGNORE”. As others have noted, this is useful for developers, but it’s non-standard, and therefore not easily portable. Another example is “GROUP CONCAT”, which has created major headaches for some developers .

Oracle of course has its share of non-standard operators as well, such as “MINUS” and “INTERSECT”.
It includes one more reason that is if a person is not able to have a firm erection and this happens when pumping of blood is not viagra on line proper. Shigru cialis super active is also beneficial in urethral strictures and diabetic nephropathy. If purchase levitra online http://canterburymewscooperative.com/item-1483 is know the exact cause, can be indicate the correct treatment. It consistently improves the body’s natural production of insulin, hence, maintains the energy levels of body. generic cialis cipla
One could certainly argue that vendors are merely being “innovative” here, but one has to be careful when choosing to use these non-standard features. MySQL does not clearly point out in their documentation when they are deviating from SQL-92. Unless you are very certain that you will never need to run your code on a new database, these functions are probably best avoided if possible.

Leave a Reply

Your email address will not be published. Required fields are marked *