Generally you have much bigger benefit with dim_STAT when you're collecting and analyzing your data live (online). However, there maybe still many situations when this is simply not possible (due security restrictions, wide remote distance, or simply externally inaccessible hosts, etc.) -- for such cases dim_STAT has special tool EasySTAT allowing you to collect all the needed stats locally on the given machine, and then later to upload them to your dim_STAT server for post-analyze. To simplify overall setup, EasySTAT is integrated into STAT-service of dim_STAT and can be directly involved from there, also following the same rules for MySQL access and so on (e.g. if your STAT-service is already operational, then your EasySTAT will be too ;-))

The following article is explaining how to deploy and start EasySTAT …

In this tutorial, we'll learn how to use React to build login, signup and logout system and Axios to send API calls and handle JWT tokens.

For building the PHP application that implements the JWT-protected REST API, check out PHP JWT Authentication Tutorial.

We'll be using the same application built in the previous tutorial as the backend for our React application we'll be building in this tutorial.

Prerequisites

You will need to have the following prerequisites to follow this tutorial step by step:

Knowledge of JavaScript, Knowledge of React, Knowledge of PHP, PHP, Composer and MySQL installed on your development machine, Node.js and NPM installed on your system.

That's it. Let's get started!

Cloning the PHP JWT App

Our example application implements JWT Authentication. It exposes three endpoints

api/login.php api/register.php api/protected.php

How to …

The MySQL Development team is proud to announce a new version of the MySQL Shell which includes the following features:

• Addition of a reporting framework:
  • API to register custom reports.
  • Shell command to display a specific report (\show).
  • Shell command to monitor a specific report (\watch).

… Facebook Twitter Google+ LinkedIn

Tweet

In my blog yesterday, I wrote about the new reporting framework in MySQL Shell. It is part of the 8.0.16 release. I also noted that it includes the possibility to create your own custom reports and use those with the \show and \watch commands. This blog will explore how you can create a report and register it, so it automatically is available when you start MySQL Shell.

Update

This blog was updated on 30 April to include the use of the values argument for report options. This moved the validation of the optional arguments in to the reporting framework and automatically includes the list of valid options …

There are three different ways ProxySQL can direct traffic between your application and the backend MySQL services.

1. Locally, on the MySQL servers.
2. Between the MySQL servers and the application.
3. Colocated on the application servers themselves.

Without going through too much detail – each has its own limitations. In the first form, the application needs to know about all MySQL servers at any given point in time. With the third form, a large number of application servers, especially in the age of Kubernetes, where apps can simply recycle easily or be scaled up and down, backend connections can increase exponentially leading to issues.

In the second form, load balancing between a pool of ProxySQL servers is normally the challenge. Do you load balance the load balancers? While there are approaches like balancing from the application, similar to how the MongoDB drivers works, the …

The MySQL 8.0.16 Release Notes are very interesting and sadly not read enough. One thing that may have escaped attention is that you no longer have to run mysql_upgrade after updating the binaries.

Let me repeat: you no longer have to run mysql_upgrade after updating the binaries. 

From the release notes:
Previously, after installation of a new version of MySQL, the MySQL server automatically upgrades the data dictionary tables at the next startup, after which the DBA is expected to invoke mysql_upgrade manually to upgrade the system tables in the mysql schema, as well as objects in other schemas such as the sys schema and user schemas.
The server, starting 8.0.16, does the work previously done by mysql_upgrade for itself.  And mysql_upgrade itself is …

The MySQL Development Team is very happy to announce a new 8.0 GA Maintenance Release of InnoDB Cluster – 8.0.16!

In addition to important bug fixes, 8.0.16 brings very useful new features!

This blog post will cover MySQL Shell and the AdminAPI, for detailed information of what’s new in MySQL Router stay tuned for an upcoming blog post!…

Facebook Twitter Google+ LinkedIn

Tweet

Readers of my blog know that I like how MySQL Shell allows you to customize it and use it’s Python and JavaScript support to create custom libraries with tools that help with your daily tasks and even creating auto-refreshing reports. Lefred has even taken this a step further and started to port …

This year we’re having a different concept for Percona Live conferences, which started at Percona Live Europe 2018 last fall. This is an approach practiced by many other organizations by having separate track for MySQL®, MongoDB®, MariaDB®, or PostgreSQL and more.

Having many tracks in this big Open Source Database Conference meant that one track steering committee could not be asked to handle all the talks for each track. So we formed several mini-committees to make sure that the submissions to each of the tracks received the right level of attention from the right kind …

MySQL 8.0.16 introduces the SQL CHECK constraint feature. This is one of the most requested and long awaited features for MySQL. This post describes the details of the feature. Let’s get started!

Introduction

The CHECK constraint is a type of integrity constraint in SQL.…

Facebook Twitter Google+ LinkedIn