PRISMADB DECRYPT not working for MySQL Database

[saklanipankaj]

PRISMADB DECRYPT t1.a;
SHOW COLUMNS FROM t1;

> Query OK, 0 rows affected (1.00 sec)

> +-------+--------------+------+------+-------------------+-------+---------------------------------+
> | Field | Type         | Null | Key  | Default           | Extra | Encryption                      |
> +-------+--------------+------+------+-------------------+-------+---------------------------------+
> | a     | double       | YES  |      | NULL              |       | Addition, Multiplication, Range |
> | b     | int          | YES  |      | NULL              |       | Addition, Multiplication, Range |
> | c     | varchar(100) | YES  |      | NULL              |       | Store, Search                   |
> | d     | timestamp    | NO   |      | CURRENT_TIMESTAMP |       | None                            |
> +-------+--------------+------+------+-------------------+-------+---------------------------------+
> 4 rows in set (0.01 sec)

There does not seem to be any change in the Encryption of the column that should no longer be encrypted any longer.

[cheziyi]

What was the result of the command PRISMADB DECRYPT t1.a STATUS?

[saklanipankaj]

+---------------------------+--------+------------------+-----------------+-----------------------------------------------------------------------------------------+
| Latest Query              | Status | Overall Progress | Column Progress | Error Message                                                                           |
+---------------------------+--------+------------------+-----------------+-----------------------------------------------------------------------------------------+
| PRISMADB DECRYPT `t1`.`a` | Error  | 0/1              | NONE            | An error has occured while modifying `t1`.`a` and any changes to it have been reverted. |
+---------------------------+--------+------------------+-----------------+-----------------------------------------------------------------------------------------+
1 row in set (0.01 sec)

[cheziyi]

Will investigate.

[cheziyi]

I am unable to repro this issue, what is the data in the table? Alternatively, you may add the ConsoleVerbose environment variable when you run the image, and set the value to 79: https://github.com/PrismaDB/PrismaDB/wiki/Configuration-Options#logging

With this, you can see the full error message, and post it here.