[MDEV-8764] Wrong error when encrypted table can't be decrypted. Created: 2015-09-07  Updated: 2015-09-14  Resolved: 2015-09-14

Status: Closed
Project: MariaDB Server
Component/s: Encryption, Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.7
Fix Version/s: 10.1.8

Type: Bug Priority: Major
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 10.1.8-1

 Description    

select * from t1;
 
ERROR 42S02: Table 'test.t1' doesn't exist in engine

Should be something like

ERROR 32S02: Table 'test.t1' encrypted and can't be decrypted



 Comments   
Comment by Jan Lindström (Inactive) [ 2015-09-08 ]

Please review at least SQL-layer changes:

http://lists.askmonty.org/pipermail/commits/2015-September/008317.html

Comment by Jan Lindström (Inactive) [ 2015-09-14 ]

commit d581ef5b2c68465815d78548357e3e104e39f5d6
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Mon Sep 14 08:27:14 2015 +0300

MDEV-8764: Wrong error when encrypted table can't be decrypted.

Add a new error message when table is encrypted but decryption
fails. Use this new error message on InnoDB/XtraDB.

Generated at Thu Feb 08 07:29:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.