Hi,
I believe I know why I get this issue but I'm just wondering if this is an expecting result of my actions or if it can be rectified.
Recently, I have implemented encryption at rest for MariaDB and I use MySQL Workbench as an environment to interact the with database. If I press on alter table on the table which has encryption on it, it will fail and give me the error message 'Error Parsing DDL for `schema`.`table`.
It will still post the SQL onto the workbench which looks like so:
delimiter $$
CREATE TABLE `tblclient` (
`ClientID` int(11) NOT NULL,
`ClientName` varchar(50) CHARACTER SET latin1 NOT NULL,
PRIMARY KEY (`ClientID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 `ENCRYPTED`=YES `ENCRYPTION_KEY_ID`=17$$
If I change the table name, it will still create the table with the encryption stated. Is this expected behaviour? Or is there are a way to fix this?
I believe I know why I get this issue but I'm just wondering if this is an expecting result of my actions or if it can be rectified.
Recently, I have implemented encryption at rest for MariaDB and I use MySQL Workbench as an environment to interact the with database. If I press on alter table on the table which has encryption on it, it will fail and give me the error message 'Error Parsing DDL for `schema`.`table`.
It will still post the SQL onto the workbench which looks like so:
delimiter $$
CREATE TABLE `tblclient` (
`ClientID` int(11) NOT NULL,
`ClientName` varchar(50) CHARACTER SET latin1 NOT NULL,
PRIMARY KEY (`ClientID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 `ENCRYPTED`=YES `ENCRYPTION_KEY_ID`=17$$
If I change the table name, it will still create the table with the encryption stated. Is this expected behaviour? Or is there are a way to fix this?