Programming logic is foundational in any application or piece of software. Without it, software wouldn’t really do much of anything. Everything happens off of choice. In the end, some truthy or falsy value is what makes stuff work. For IF/THEN/ELSE logic in standard SQL, there is the CASE expression. There are 2 variations of the CASE Expression: Simple and Searched. In this post, I cover the Simple MySQL CASE expression with example queries…

Image by Nika Akin from …

The first tutorial supplementing the MySQL Connector/NET Developer Guide showed you how to connect and run static INSERT statement. It was a barebones PowerShell script with the MySQL Connector. This post shows you how to run a PowerShell script that uses a dynamic form to gather the MySQL credentials and then run a static query. Below is the MySQL Credentials form.

You enter the correct user name, password, hostname (or IP address), port, and database, like this:

Here’s the complete code for this staticQuery.ps1 PowerShell script:

# Add libraries for form components. …

It was interesting to note that the MySQL Connector/NET Developer Guide doesn’t have any instructions for connecting to the MySQL database from Microsoft Powershell. I thought it would be helpful to write a couple demonstrations scripts, especially when a quick search didn’t find a set of easy to follow samples.

The connection process to MySQL with Powershell is easiest with a non-query, so I created a db_connect table into which I could write a row of data:

CREATE TABLE db_connect
( db_connect_id  INT UNSIGNED PRIMARY KEY AUTO_INCREMENT
, version        VARCHAR(10)
, user           VARCHAR(24)
, db_name        VARCHAR(10));

The following insert.ps1 PowerShell script connects to the MySQL database, and inserts one row into the db_connect table:

# Connect to the libaray …

Join us on Wednesday April 28th, 2021 @9:00AM PST for a live webinar that will cover how to migrate from Amazon Aurora to MySQL Database Service and HeatWave.

See how you can easily migrate your data from Amazon Aurora to MySQL Database Service and benefit from 1100x performance increase at 1/3 the cost, right away.

You will takeaway quick steps and best practices for your database migration.
 

Register now!

Learn more about MysQL Database Service

…

Join us on Wednesday April 28th, 2021 @9:00AM PST for a live webinar that will cover how to migrate from Amazon Aurora to MySQL Database Service and HeatWave. See how you can easily migrate your data from Amazon Aurora to MySQL Database Service and benefit from 1100x performance increase at 1/3 the ...

Join us on Thursday April 29th, 2021 @10:00 CET (EMEA) for a live webinar that will cover the new features of MySQL Enterprise Edition.  

Who's the event for? 

• Your applications manage personal data: name, account numbers, passwords 
• You belong to an industry or region that is subject to data protection requirements
• You use 3rd party components for authentication, auditing, & key management
• You're an ISVs and SaaS organization that manages sensitive customer data
• You're an existing MySQL Community Edition user

Learn how MySQL Enterprise Edition will save you time and give you piece of mind by increasing the protection of your critical data, the prevention of data breaches and by helping you meet regulator requirements.

MySQL …

Join us on Thursday April 29th, 2021 @10:00 CET (EMEA) for a live webinar that will cover the new features of MySQL Enterprise Edition. Who's the event for? Your applications manage personal data: name, account numbers, passwords You belong to an industry or region that is subject to data protection...

On behalf of the Vitess maintainers, I am pleased to announce the general availability of Vitess 10. Major Themes # In this release, Vitess Maintainers have continued to focus on compatibility. It is still the most critical component of Vitess being part of the MySQL ecosystem. We have also started working on benchmarking and performance optimizations. These improvements have given us a clear vision of which areas of Vitess can be improved in terms of performance.

Apologies for the silly title, but the issue is a real one, even though it is not a new thing. Schema upgrades are not an ordinary operation in Galera. For the subject at hand, the bottom line is: under the default Total Order Isolation (TOI) method, “the cluster replicates the schema change query as a statement before its execution.” What this means in practice is that a DDL issued in one node is replicated to other nodes in the cluster before it is even executed in the source node, let alone completed successfully.

As a result of this, it may fail in one node and be successful in another, and this without raising loud alerts or stopping nodes to protect against data inconsistency. This is not a bug in itself but rather a compromise of design. With new changes in MySQL and the …

Recently I posted an article on how to deal with arrays when trying to use MySQL Shell Dump Utility in command line.

Of course, this proposed solution was a workaround for MySQL Shell <= 8.0.23. The new version of MySQL Shell 8.0.24 supports now arrays \o/ !

So if we take the same example of the previous post, we can now use the following syntax:

$ mysqlsh root@localhost -- util dump-instance /tmp/dump \
    --excludeSchemas=["mysql_innodb_cluster_metadata","fred_test"] \
    --threads=8 --showProgress

Please mind that lack of <space> between the elements of the array. If you use …