As Scalingo for MySQL® is a fully managed service, we enforce certain operational limits and usage policies to maintain reliability and security for all users.

Affecting User Management

• Updating the protected user’s password is not supported. Please get in touch with our support team to refresh this password.

Affecting Features

• When using a Business plan, the secondary nodes of the cluster are not accessible. These instances are only present to ensure high-availability. They are not meant to plug analysis tools, even in read-only mode.

Requirements

• Starting with MySQL® version 8, every table must have a primary key.
  Here is an example of a SQL statement adding a new column and setting it as primary (impact of this modification must be evaluated before proceeding):

  ALTER TABLE 'foo' ADD COLUMN <column name> PRIMARY KEY;
  

Timeouts

Scalingo for MySQL® addons have, depending on the plan, one or two MySQL® Router instances as entry point. These instances have a few timeouts which may impact your application. We don’t customize these timeouts, so that default values are kept.

For further details about these timeouts, please check the official documentation for MySQL® Router, depending on your MySQL® version:

• For MySQL® 8.0