18.11.2015 22:32, Dmitry Yemanov wrote:
>> >as long as UUID and Crypt Database ID are understood to be separate values
> Here I completely agree.
Ok, I, actually, don't care which one my plugin will get. All I need is
something for
key holder to make decision which key it must return.
Provide better information for "Invalid expression in the select list (not
contained in either an aggregate function or the GROUP BY clause)"
-
Provide better message for - Adding Not null field without default - error
"This operation is not defined for system tables"
Key: CORE-5023
18.11.2015 19:31, Alex Peshkoff wrote:
>> >I think we need to step back and decide what the real problem is trying to
>> >be solved!!!
> Yes.
In this case the "real problem" is a ticket in tracker with feature request.
--
WBR, SD.
Hello, All.
I've finished some modifications in database encryption system:
Crypt plugin interface was made simpler.
Database id generated at creation time is provided to it.
Key holder interface was made simpler.
Management of key holders was moved to Y-valve that enabled
