 |
The federated table editing module is called in the table list | |
|
|---|
 |
Module for editing MySQL Federated tables:
|
| Display information and data of the table. |
| Table structure and table options cannot be edited. |
| Tools for copying and deleting data and structure. |
| Backup to SQL script archive of table and manage files.
|
|
| Table header: |
| Name: | Name of the new table |
| Comment: | Comment to be stored for the table. |
| Next autoindex: | Omitted for federated tables. |
| Engine: | Database format of the table (FEDERATED). |
| Sorting: | Character set and collation of the table. |
| Row format: | Format in which the table rows should be managed in the database. |
| |
| Table columns: |
| Name: | Column Name |
| Type: | Data type of the column. |
| Length/Value: | Storage size or format of the data type. |
|
 |
Table is reloaded. |
 |
Display table information. |
 |
View and edit table data. |
 |
Data wizard to view and edit data. |
 |
Display form for inserting new data records. |
 |
Module to import data into MySQL table. |
 |
Editing table options. |
 |
Edit database user permissions to table. |
|
 |
Save table definition and data in the archive. |
 |
Download table definition and data. |
 |
Display table archive. |
|
 |
Display table tools. |
 |
Display elete functions. |
|
 |
|
Labeled menu by double-clicking title bar.
|
| Save table definition and data in the archive: |
 |
Saving the table creation script and data to the MyWAY SQL Manager archive.
|
| Table definition: | Table creation script is saved. |
| Table data: | Table data is saved as a SQL script. |
| GZIP: | Files are saved with GZip compression. |
|
| Download table definition and data: |
 |
Download the table creation script and data.
|
| Table definition: | Download the table creation script. |
| Table data: | Download the table data. |
| GZIP: | Files are downloaded with GZip compression. |
|
MySQL and MariaDB Federated Tables is a storage engine that accesses data from a remote MySQL server or Remote MariaDB Server to edit them as if they were local tables. It provides a way to create virtual tables that act as proxies for tables on another MySQL and MariaDB server, thus enabling distributed queries and enable data integration.
In federated tables, data can be queried and modified without having to replicate the data or transfer it to the local server. Changes to the data in a federated table on the local server are immediately reflected on the remote server. This ensures data consistency between the two servers. Standard SQL queries can be used to retrieve data from federated tables. The local server sends the query to the remote server, which processes it and returns the result set to the local server. Federated tables support insert, update, and delete operations. These operations are performed transparently on the remote server through the Federated table.
When a federated table is created, its structure (column names, data types, constraints) is defined to match the structure of the remote table. The federated table acts as a proxy and represents the remote table on the local server. The user account used to access the federated table must have appropriate permissions on both the local and remote servers. The remote server may need additional permissions to access the remote table.
There are some limitations to be aware of with joined tables. For example, federated table transactions are not supported and the remote table must be accessible and properly configured on the remote server. To create a federated table, specify the FEDERATED storage engine and the remote table connection details in the table definition.
MySQL and MariaDB Federated Tables make sense when storing data from remote MySQL servers in a single database integrated and queried. They provide a convenient way to access and manipulate data in distributed environments without the need for replication or synchronization. |
