I am the author of High Performance My SQL and lots of open-source software for performance analysis, monitoring, and system administration.
I contribute to various database communities such as Oracle, Postgre SQL, Redis and Mongo DB.
If performance is the goal and the queries don’t need to be portable, I see no reason not to use the solution that performs best.
However, if you really do need to execute that query (or if all your fruit really has turned into bananas), you can do one of the following: It's always a good idea to restore the setting to its previous state once you're done — especially with settings that could have a widespread impact like this one.
Here's the code we used when we created that column: However, you might encounter the following error if you try to do that: If you encounter the above error, it's because your My SQL connection is running in Safe Updates mode.
This helps prevent us from overwriting large amounts of data accidentally.
I belive fully portable or “platform-independent” SQL is mostly a myth.
Writing generic “standard” SQL to the lowest common denominator almost certainly results in under-utilizing the RDBMS’s abilities.
In this article I’ll give an overview of each feature, help you understand how to choose among them, and point out some things to watch out for. I assume My ISAM tables without support for transactions, with the following sample data: create table t1 ( a int not null primary key, b int not null, c int not null ) type=My ISAM; create table t2 ( d int not null primary key, e int not null, f int not null ) type=My ISAM; insert into t1 (a, b, c) values (1, 2, 3), (2, 4, 6), (3, 6, 9); insert into t2 (d, e, f) values (1, 1, 1), (4, 4, 4), (5, 5, 5);.