(Giuseppe Maxia) As everyone knows, I am a command line guy. I am very much comfortable with the shell prompt and the command line SQL client. I do most of my work that way, and I am very much productive.

(Michael McLaughlin) I overlooked MySQL’s real equivalent to a MERGE statement, which is the REPLACE INTO statement. A previous example uses the INSERT statement with the ON DUPLICATE KEY clause. The following demonstrates how to perform a left join from and exernal source.

(Joshua Tolley) PostgreSQL is well known for its extensibility; users can build new functions, operators, data types, and procedural languages, among others, without having to modify the core PostgreSQL code. Less well known is PostgreSQL’s extensive set of “hooks”, available to the more persistent

(Mark Callaghan) How do you get more throughput from a workload that has a lot of concurrency and transactions that contend on updating the same rows? Move the updates for the contended rows to the end of the transaction. This is a good problem to prevent as it is very hard to diagnose on production

(Peter Eisentraut) The SQL MERGE statement has gotten my attention again. For many years, PostgreSQL users have been longing for a way to do an "upsert" operation, meaning do an UPDATE, and if no record was found do an INSERT (or the other way around).

(Marko Sutic) At the end of partial restore of database I’ve noticed entries MISSING00008, MISSING00009, etc. Oracle created those entries because some datafiles were found in data dictionary but not in new controlfile.

(Venu Anuganti) Lately in the MySQL community, we only hear about scalability or performance improvements of storage engines, but nothing about query engine itself. For example, one classic example being InnoDB; if we look back all the scalability issues that community reported a year back or even f

(Shlomi Noach) I’m further developing a general log hook, which can stream queries from the general log.

(Rob Gravelle) Although there is no direct support for dynamic declaration of column and table names in MySQL stored procedures, by utilizing user variables and prepared statements we can achieve the same result. In the MySQL Input Parameters Add Flexibility to Crosstab Stored Procedures article, we

(Ronald Bradford) There have been a few posts by Sheeri and Baron today on the MySQL sort_buffer_size variable. I wanted to add some more information about this buffer, what is impacted when it is changed, and what to do about it?