Skip to content

Commit b050a17

Browse files
committed
Learn Editor: Update whats-new.md
1 parent b654dc9 commit b050a17

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mysql/flexible-server/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This article summarizes new releases and features in Azure Database for MySQL -
3030
- **Universal Geo Restore in Azure Database for MySQL - Flexible Server (Public Preview)**
3131
Universal Geo Restore feature will allow you to restore a source server instance to an alternate region from the list of Azure supported regions where flexible server is [available](./overview.md#azure-regions). If a large-scale incident in a region results in unavailability of database application, then you can use this feature as a disaster recovery option to restore the server to an Azure supported target region, which is different than the source server region. [Learn more](concepts-backup-restore.md#restore)
3232

33-
- **Universal Geo Restore in Azure Database for MySQL - Flexible Server (Public Preview)**
33+
- **Generated Invisible Primary Key in Azure Database for MySQL - Flexible Server**
3434
Azure Database for MySQL Flexible Server now supports generated invisible primary key (GIPK) mode for MySQL version 8.0. With this change, by default, the value of the server system variable "sql_generate_invisible_primary_key" is ON for all MySQL - Flexible Server on MySQL 8.0. With GIPK mode ON, MySQL generates an invisible primary key to any InnoDB table which is new created without an explicit primary key. Learn more about the GIPK mode:
3535
[Generated Invisible Primary Keys](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html)
3636
[Invisible Column Metadata](https://dev.mysql.com/doc/refman/8.0/en/invisible-columns.html#invisible-column-metadata)

0 commit comments

Comments
 (0)