[MDEV-4912] Data type plugin API version 1 - Jira

roberto spadim created issue - 2013-08-17 20:48

roberto spadim made changes - 2013-08-17 20:48

Field	Original Value	New Value
Link		This issue relates to ~~MDEV-4631~~ [ ~~MDEV-4631~~ ]

roberto spadim made changes - 2013-08-17 20:48

Link

This issue relates to ~~MDEV-274~~ [ ~~MDEV-274~~ ]

roberto spadim made changes - 2013-08-17 20:53

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin.

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name
2)plugin version
3)plugin column type name
4)plugin column options

let'me explain with a example based:
{code}
PLUGIN('CRYPT','1','SHA1',"PASSWORD=ABCDEFG,SIZE=255")
{code}
this kind of plugin, with name CRYPT, version 1, will use a SHA1 algorithm to crypt/decrypt information from disk, based in a varchar(255) field type
internally plugin will have function to;
1) send what bytes should be write, and what kind of field type will be used, here it will use normal mysql field types (VARCHAR,CHAR,INT,FLOAT,BLOB,TEXT,DECIMAL,DATE,DATETIME,TIME,GEOMETRY ...)
2) read values from database
3) compare values
4) maybe optimize the <field> <operator> <constant> operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) |

it's a raw idea, and must be better checked, the main high level idea is here, low level should be considered before start work

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin.

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

*THE FRM FILE WILL STORE THE PLUGIN FIELD TYPE, AND THE "INTERNAL ENGINE" TYPE, WHEN WE CAN'T LOAD THE PLUGIN WE COULD AT LEAST READ THE ENGINE INFORMATION INSTEAD OF A "CRASHED TABLE" PROBLEM*

let'me explain with a example based:
{code}
PLUGIN('CRYPT','1','SHA1',"PASSWORD=ABCDEFG,SIZE=255")
{code}
this kind of plugin, with name CRYPT, version 1, will use a SHA1 algorithm to crypt/decrypt information from disk, based in a varchar(255) field type
internally plugin will have function to;
1) send what bytes should be write, and what kind of field type will be used, here it will use normal mysql field types (VARCHAR,CHAR,INT,FLOAT,BLOB,TEXT,DECIMAL,DATE,DATETIME,TIME,GEOMETRY ...)
2) read values from database
3) compare values
4) maybe optimize the <field> <operator> <constant> operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) |

it's a raw idea, and must be better checked, the main high level idea is here, low level should be considered before start work

more considerations about differente versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example, the plugin could read the old value, and write the new value, just a idea... the version is the same version parameter of PLUGIN field type, is the same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS"

roberto spadim made changes - 2013-08-17 20:56

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin.

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

*THE FRM FILE WILL STORE THE PLUGIN FIELD TYPE, AND THE "INTERNAL ENGINE" TYPE, WHEN WE CAN'T LOAD THE PLUGIN WE COULD AT LEAST READ THE ENGINE INFORMATION INSTEAD OF A "CRASHED TABLE" PROBLEM*

let'me explain with a example based:
{code}
PLUGIN('CRYPT','1','SHA1',"PASSWORD=ABCDEFG,SIZE=255")
{code}
this kind of plugin, with name CRYPT, version 1, will use a SHA1 algorithm to crypt/decrypt information from disk, based in a varchar(255) field type
internally plugin will have function to;
1) send what bytes should be write, and what kind of field type will be used, here it will use normal mysql field types (VARCHAR,CHAR,INT,FLOAT,BLOB,TEXT,DECIMAL,DATE,DATETIME,TIME,GEOMETRY ...)
2) read values from database
3) compare values
4) maybe optimize the <field> <operator> <constant> operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) |

it's a raw idea, and must be better checked, the main high level idea is here, low level should be considered before start work

more considerations about differente versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example, the plugin could read the old value, and write the new value, just a idea... the version is the same version parameter of PLUGIN field type, is the same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS"

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

*THE FRM FILE WILL STORE THE PLUGIN FIELD TYPE, AND THE "INTERNAL ENGINE" TYPE, WHEN WE CAN'T LOAD THE PLUGIN WE COULD AT LEAST READ THE ENGINE INFORMATION INSTEAD OF A "CRASHED TABLE" PROBLEM*

let'me explain with a example based:
{code}
PLUGIN('CRYPT','1','SHA1',"PASSWORD=ABCDEFG,SIZE=255")
{code}
this kind of plugin, with name CRYPT, version 1, will use a SHA1 algorithm to crypt/decrypt information from disk, based in a varchar(255) field type
internally plugin will have function to;
1) send what bytes should be write, and what kind of field type will be used, here it will use normal mysql field types (VARCHAR,CHAR,INT,FLOAT,BLOB,TEXT,DECIMAL,DATE,DATETIME,TIME,GEOMETRY ...)
2) read values from database
3) compare values
4) maybe optimize the <field> <operator> <constant> operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) |

more considerations about differente versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example, the plugin could read the old value, and write the new value, just a idea... the version is the same version parameter of PLUGIN field type, is the same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS"

roberto spadim added a comment - 2013-08-17 21:00

We have some nice field type in PostgreSQL
THE MAIN PROBLEM ABOUT THIS PLUGIN IS A NOT STANDARD ABOUT FIELD TYPES...
for example XML functions of MYSQL 5.7 want a VARCHAR/CHAR/TEXT/BLOB as parameter, and a XML type could make some incompatibility...

well more definition is need before add more considerations...

roberto spadim added a comment - 2013-08-17 21:00 We have some nice field type in PostgreSQL THE MAIN PROBLEM ABOUT THIS PLUGIN IS A NOT STANDARD ABOUT FIELD TYPES... for example XML functions of MYSQL 5.7 want a VARCHAR/CHAR/TEXT/BLOB as parameter, and a XML type could make some incompatibility... well more definition is need before add more considerations...

roberto spadim made changes - 2013-08-17 21:00

Remote Link

This issue links to "PostgreSQL field type (Web Link)" [ 12105 ]

roberto spadim made changes - 2013-08-17 21:16

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

*THE FRM FILE WILL STORE THE PLUGIN FIELD TYPE, AND THE "INTERNAL ENGINE" TYPE, WHEN WE CAN'T LOAD THE PLUGIN WE COULD AT LEAST READ THE ENGINE INFORMATION INSTEAD OF A "CRASHED TABLE" PROBLEM*

let'me explain with a example based:
{code}
PLUGIN('CRYPT','1','SHA1',"PASSWORD=ABCDEFG,SIZE=255")
{code}
this kind of plugin, with name CRYPT, version 1, will use a SHA1 algorithm to crypt/decrypt information from disk, based in a varchar(255) field type
internally plugin will have function to;
1) send what bytes should be write, and what kind of field type will be used, here it will use normal mysql field types (VARCHAR,CHAR,INT,FLOAT,BLOB,TEXT,DECIMAL,DATE,DATETIME,TIME,GEOMETRY ...)
2) read values from database
3) compare values
4) maybe optimize the <field> <operator> <constant> operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) |

more considerations about differente versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example, the plugin could read the old value, and write the new value, just a idea... the version is the same version parameter of PLUGIN field type, is the same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS"

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE"

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

roberto spadim made changes - 2013-08-17 21:20

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE"

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

roberto spadim made changes - 2013-08-17 21:21

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters, the point here is only the FIELD TYPE,others parameters will exists, and will be used when possible, but plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement
{code}

<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

roberto spadim made changes - 2013-08-17 21:21

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters, the point here is only the FIELD TYPE,others parameters will exists, and will be used when possible, but plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement
{code}

<plugin info> will be saved at .FRM file, and informations here are:
1)plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
2)plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
3)plugin column type name (internal to plugin code)
4)plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters, the point here is only the FIELD TYPE,others parameters will exists, and will be used when possible, but plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement
{code}

<plugin info> will be saved at .FRM file, and informations here are:
#plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
#plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
#plugin column type name (internal to plugin code)
#plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

roberto spadim made changes - 2013-08-17 21:33

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters, the point here is only the FIELD TYPE,others parameters will exists, and will be used when possible, but plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement
{code}

<plugin info> will be saved at .FRM file, and informations here are:
#plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
#plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
#plugin column type name (internal to plugin code)
#plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command

the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
0=> don't open, report an error
1=> open, and report a warning
2=> open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and "INTERNAL TYPE"=varchar(255)

internally plugin will have function to: *(must be better defined)*

1) read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
2) read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
3) compare values could/should/must be pass via PLUGIN, for example if we want a ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, a select query to solve this, like:

SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1

4) optimize the "<field> <operator> <constant>" where operations

there's some problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just read the CREATE TABLE
we could add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

more considerations about different versions of the same plugin:
we could add a 'automatic' alter table, when one plugin is upgrade from version 1 to version 2 for example
the plugin could read the old value, and write the new value, just an idea...

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
# the point here is only the FIELD TYPE, others parameters will exist, and will be used when possible, plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement

<plugin info> will be saved at .FRM file, and informations are:
# plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
# plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
# plugin column type name (internal to plugin code)
# plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command and others information_schemas tables

we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
# don't open, report an error
# open, and report a warning
# open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

# POINT TO THINK* -> We can DUMP/RESTORE a table faster if we don't use the plugin interface, just the engine information, maybe a *DISABLE FIELD PLUGIN* before a DUMP/RESTORE could help a lot here, and allow a WRITE without using the plugin interface

---
Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and size, the "INTERNAL TYPE" calculated will be a varchar(255), the storage type is a BLOB column, and the index type is a BLOB column too (check that some times we can use VARCHAR(255) since the index can't use BLOB, but a VARCHAR(255) is allowed... we could for example crypt the STORAGE and leave the index uncrypted... just a plugin feature but in this case a security problem)

internally plugin will have function to: *(must be better defined)*

# read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
# read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
# compare values could/should/must pass PLUGIN, for example if we want a EXTERNAL_ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, for example
PLUGIN('EXTERNAL_ENUM','1','KEY','DATABASE=some_database,TABLE=some_table,KEY=some_column,VALUE=some_column')
and the plugin will execute a select query to solve the translation between INTERNAL and STORAGE TYPES, like:
{code}
SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1
{code}
# optimize the "<field> <operator> <constant>" where operations, here the EXTERNAL_ENUM could return ALWAYS FALSE, or ALWAYS TRUE

there's some client side problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just reading the CREATE TABLE information
we must add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

*more considerations about different versions of the same plugin*
we could add a 'automatic' alter table feature to upgrade a plugin field from version 1 to version 2 for example

current field information:
CREATE TABLE a (field PLUGIN('plugin','1','column','parameters'))
new field information:
ALTER TABLE a (field PLUGIN('plugin','2','column','parameters'))

the plugin could read the old value, and write the new value, just an idea, the first problem here is the WRONG PLUGIN VERSION ERROR, we could read the METAINFORMATION (SHOW FIELD, SHOW CREATE TABLE), but we cant read the data (check "open_table_without_field_plugin_definition" variable), but in this case we can upgrade the field definition via alter table

the plugin will return something like "don't change anything" or "must change table" or "can't upgrade table" to alter table command

roberto spadim made changes - 2013-08-17 21:40

Link

This issue relates to MDEV-4913 [ MDEV-4913 ]

roberto spadim made changes - 2013-08-17 22:48

Link

This issue relates to MDEV-4913 [ MDEV-4913 ]

roberto spadim made changes - 2013-08-17 22:48

Link

This issue blocks MDEV-4913 [ MDEV-4913 ]

Sergei Golubchik made changes - 2013-08-18 10:18

Fix Version/s

10.1.0 [ 12200 ]

roberto spadim made changes - 2013-08-29 04:51

Link

This issue relates to ~~MDEV-4958~~ [ ~~MDEV-4958~~ ]

Sergei Golubchik made changes - 2014-03-03 15:14

Labels

gsoc14

Sergei Golubchik made changes - 2014-03-03 15:15

Link

This issue relates to MDEV-4405 [ MDEV-4405 ]

Sergei Golubchik made changes - 2014-03-03 15:17

Link

This issue relates to ~~MDEV-5593~~ [ ~~MDEV-5593~~ ]

Sergei Golubchik made changes - 2014-04-17 18:30

Description

This MDEV will allow a plugin for field types, there's many MDEV and ideas over mysql/mariadb/percona/others forks, that want IPv6, Encrypted column, and others features, this is nice, but add many non standard code (but native code), the idea is allow this to be a plugin, and not a native code.

*THIS MDEV IS A RAW IDEA, and MUST BE CHECKED! the main high level idea is here, low level should be considered before start work*

based on PostgrSQL definition "built-in general-purpose data types" is something that all MYSQL ENGINES know about field type, theses types is the current mysql types, and should be used by this field plugin.
I WILL CALL IT AS "INTERNAL TYPE", TO STORAGE ENGINE I WILL CALL IT AS "STORAGE TYPE" AND FOR INDEX I WILL CALL IT AS "INDEX TYPE"

---

for Alter table sintax we will have:
{code}
ALTER TABLE TABLE ...
ADD field_name
PLUGIN(<plugin info-1>,<plugin info-2>,<plugin info-3>,<plugin info-4>)
NOT NULL/NULL
AUTOINCREMENT
DEFAULT
... others field parameters
{code}
# the point here is only the FIELD TYPE, others parameters will exist, and will be used when possible, plugin will return a error if it don't support for example a default value, or a not null, null or autoincrement

<plugin info> will be saved at .FRM file, and informations are:
# plugin name (same value of "SELECT PLUGIN_NAME FROM information_schema.PLUGINS")
# plugin version (same value of "SELECT PLUGIN_VERSION FROM information_schema.PLUGINS")
# plugin column type name (internal to plugin code)
# plugin column options (internal to plugin code)

The plugin will "calculate" the "INTERNAL TYPE", "STORAGE TYPE", "INDEX TYPE" to be used
# the FRM file will store the "FIELD TYPE", "STORAGE TYPE", "INDEX TYPE", "INTERNAL TYPE"
# We must check if we need a *STORAGE TYPE* and a "INDEX TYPE", based that some colations could be used, and some optimizations could be used, index could be encrypted or for example we could write a string to storage, and a integer to index, *must check if this is possible with today internal mysql code*

This information will be added to SHOW COLUMN command and others information_schemas tables

we must add a global variable, "open_table_without_field_plugin_definition" it have 3 values:
# don't open, report an error
# open, and report a warning
# open and don't report anything
check that (1 and 2) make the table READ ONLY !!!! *we can't WRITE without the plugin loaded!!!*

# POINT TO THINK* -> We can DUMP/RESTORE a table faster if we don't use the plugin interface, just the engine information, maybe a *DISABLE FIELD PLUGIN* before a DUMP/RESTORE could help a lot here, and allow a WRITE without using the plugin interface

---
Let'me explain with a example how the plugin parameters should be used:
{code}
PLUGIN(
'CRYPT',
'1',
'SHA1',
"PASSWORD=ABCDEFG,SIZE=255"
)
{code}
this kind of plugin, with name "CRYPT", version "1", will use a "SHA1" column (maybe a algorithm to crypt/decrypt information from disk), with parameters about password and size, the "INTERNAL TYPE" calculated will be a varchar(255), the storage type is a BLOB column, and the index type is a BLOB column too (check that some times we can use VARCHAR(255) since the index can't use BLOB, but a VARCHAR(255) is allowed... we could for example crypt the STORAGE and leave the index uncrypted... just a plugin feature but in this case a security problem)

internally plugin will have function to: *(must be better defined)*

# read bytes from storage engine (STORAGE/INDEX TYPE) and send "decoded" field to mysql core (INTERNAL TYPE)
# read bytes from mysql core (INTERNAL TYPE) and send "encoded" bytes to storage engine (STORAGE/INDEX TYPE)
# compare values could/should/must pass PLUGIN, for example if we want a EXTERNAL_ENUM field plugin to use a external table as KEY(int)=>VALUE(string), we can call via PLUGIN interface, for example
PLUGIN('EXTERNAL_ENUM','1','KEY','DATABASE=some_database,TABLE=some_table,KEY=some_column,VALUE=some_column')
and the plugin will execute a select query to solve the translation between INTERNAL and STORAGE TYPES, like:
{code}
SELECT VALUE FROM TABLE WHERE VALUE="ID"
UNION
SELECT VALUE FROM TABLE WHERE KEY="ID"
LIMIT 1
{code}
# optimize the "<field> <operator> <constant>" where operations, here the EXTERNAL_ENUM could return ALWAYS FALSE, or ALWAYS TRUE

there's some client side problems.... first one, user interfaces (heidisql for example) will not know what type of information it will have just reading the CREATE TABLE information
we must add more information to "SHOW COLUMNS FROM <table>", example:
|| *Field* || *Type* || *Null* || *Key* || *Default* || *Extra* || *Internal Type* || *Storage Type* || *Index Type* ||
| ID | PLUGIN('CRYPT','1','SHA1','PASSWORD=ABCEDFG,SIZE=255') | NO | | 0 | | VARCHAR(255) | BLOB | BLOB |

*more considerations about different versions of the same plugin*
we could add a 'automatic' alter table feature to upgrade a plugin field from version 1 to version 2 for example

current field information:
CREATE TABLE a (field PLUGIN('plugin','1','column','parameters'))
new field information:
ALTER TABLE a (field PLUGIN('plugin','2','column','parameters'))

the plugin could read the old value, and write the new value, just an idea, the first problem here is the WRONG PLUGIN VERSION ERROR, we could read the METAINFORMATION (SHOW FIELD, SHOW CREATE TABLE), but we cant read the data (check "open_table_without_field_plugin_definition" variable), but in this case we can upgrade the field definition via alter table

the plugin will return something like "don't change anything" or "must change table" or "can't upgrade table" to alter table command

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

Sergei Golubchik made changes - 2014-04-17 18:31

Description

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

_see the original issue description in the history_

Sergei Golubchik made changes - 2014-04-17 18:36

Description

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

_see the original issue description in the history_

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

*This task doesn't cover everything!* It is assumed that we can expand this API later to add more features. In particular, the following is not solved:
* data types that cannot be efficiently memcmp()'ed. For example, this proposal doesn't allow to implement a string type with charset support.
* data types that require special indexes, such as XML, spatial data, etc.

_see the original issue description in the history_

Sergei Golubchik made changes - 2014-04-17 18:36

Description

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

*This task doesn't cover everything!* It is assumed that we can expand this API later to add more features. In particular, the following is not solved:
* data types that cannot be efficiently memcmp()'ed. For example, this proposal doesn't allow to implement a string type with charset support.
* data types that require special indexes, such as XML, spatial data, etc.

_see the original issue description in the history_

Issues to solve:
* read/write: that's easy, the plugin provides some kind of a "store" method that serializes the data into something that can be memcmp-ed. And "val" methods as appropriate.
* indexing: not at issue, the engine thinks the column type is BINARY and indexes is accordingly
* don't forget that field definition may use parameters, like in VARCHAR(10)
* protocol
** text protocol - what to send as field metadata? variant: MYSQL_TYPE_PLUGIN and a string with the type name
** binary protocol - how to send the value to the client: variant: as a string. how the client send the value to the server? either way, the server converts it from number/string/etc just as for INSERTs
* replication, RBR
** similar, use MYSQL_TYPE_PLUGIN, and as additional metadata - field type as a string, parameters, whatever

So, a plugin would need to provide
* store() method from at least some of the basic types
* val() methods to at least some of the basic types
* description of whatever parameters a field definition takes
* informational methods, like store_length(), etc

*This task doesn't cover everything!* It is assumed that we can expand this API later to add more features. In particular, the following is not solved:
* data types that cannot be efficiently memcmp()'ed. For example, this proposal doesn't allow to implement a string type with charset support.
* data types that require special indexes, such as XML, spatial data, etc.

_see also the original issue description in the history_

Sergei Golubchik made changes - 2014-04-21 13:07

Assignee

Alexander Barkov [ bar ]

Daniel Bartholomew made changes - 2014-05-16 12:36

Fix Version/s		10.1.1 [ 16100 ]
Fix Version/s	10.1.0 [ 12200 ]

Sergei Golubchik made changes - 2014-06-13 15:06

Workflow

defaullt [ 28427 ]

MariaDB v2 [ 43674 ]

Sergei Golubchik made changes - 2014-08-08 20:30

Priority

Major [ 3 ]

Minor [ 4 ]

Alexander Barkov made changes - 2014-10-21 16:08

Status

Open [ 1 ]

In Progress [ 3 ]

Sergei Golubchik made changes - 2015-04-20 07:47

Link

This issue duplicates ~~MDEV-7931~~ [ ~~MDEV-7931~~ ]

Alexander Barkov made changes - 2015-05-04 07:15

Link

This issue blocks ~~MDEV-8092~~ [ ~~MDEV-8092~~ ]

Alexander Barkov made changes - 2015-05-04 07:44

Link

This issue is blocked by MDEV-8095 [ MDEV-8095 ]

Rasmus Johansson (Inactive) made changes - 2015-05-18 17:51

Workflow

MariaDB v2 [ 43674 ]

MariaDB v3 [ 67312 ]

Sergei Golubchik made changes - 2015-06-18 10:40

Fix Version/s		10.2 [ 14601 ]
Fix Version/s	10.1 [ 16100 ]

Alexander Barkov made changes - 2015-10-11 12:30

Labels

gsoc14

Sergei Golubchik made changes - 2015-10-11 15:13

Labels

gsoc14

Sergei Golubchik made changes - 2015-11-09 20:56

Link

This issue is blocked by ~~MDEV-8092~~ [ ~~MDEV-8092~~ ]

Sergei Golubchik made changes - 2015-11-09 20:56

Link

This issue blocks ~~MDEV-8092~~ [ ~~MDEV-8092~~ ]

Sergei Golubchik made changes - 2015-11-09 20:56

Link

This issue blocks ~~MDEV-4958~~ [ ~~MDEV-4958~~ ]

Sergei Golubchik made changes - 2015-11-09 20:56

Link

This issue relates to ~~MDEV-4958~~ [ ~~MDEV-4958~~ ]

Sergei Golubchik made changes - 2015-11-09 20:57

Link

This issue blocks ~~MDEV-274~~ [ ~~MDEV-274~~ ]

Sergei Golubchik made changes - 2015-11-09 20:57

Link

This issue relates to ~~MDEV-274~~ [ ~~MDEV-274~~ ]

Sergei Golubchik made changes - 2015-11-17 16:42

Link

This issue is blocked by ~~MDEV-9144~~ [ ~~MDEV-9144~~ ]

Rasmus Johansson (Inactive) made changes - 2015-11-17 17:52

Sprint

10.2.0-1 [ 21 ]

Rasmus Johansson (Inactive) made changes - 2015-11-17 17:52

Rank

Ranked lower

Alexander Barkov made changes - 2015-11-23 16:57

Link

This issue relates to ~~MDEV-9170~~ [ ~~MDEV-9170~~ ]

Alexander Barkov made changes - 2015-11-23 16:57

Link

This issue relates to ~~MDEV-9170~~ [ ~~MDEV-9170~~ ]

Alexander Barkov made changes - 2015-11-23 16:57

Link

This issue is blocked by ~~MDEV-9170~~ [ ~~MDEV-9170~~ ]

Alexander Barkov made changes - 2015-11-25 12:24

Link

This issue is blocked by ~~MDEV-9188~~ [ ~~MDEV-9188~~ ]

Alexander Barkov made changes - 2015-11-30 14:39

Link

This issue is blocked by ~~MDEV-9211~~ [ ~~MDEV-9211~~ ]

Alexander Barkov made changes - 2015-12-01 09:22

Link

This issue is blocked by ~~MDEV-9215~~ [ ~~MDEV-9215~~ ]

Alexander Barkov made changes - 2015-12-01 10:42

Link

This issue is blocked by ~~MDEV-9144~~ [ ~~MDEV-9144~~ ]

Alexander Barkov made changes - 2015-12-01 10:43

Link

This issue relates to ~~MDEV-9056~~ [ ~~MDEV-9056~~ ]

Alexander Barkov made changes - 2015-12-01 10:46

Link

This issue relates to ~~MDEV-9216~~ [ ~~MDEV-9216~~ ]

Alexander Barkov made changes - 2015-12-01 10:47

Link

This issue relates to ~~MDEV-9216~~ [ ~~MDEV-9216~~ ]

Alexander Barkov made changes - 2015-12-01 10:47

Link

This issue is blocked by ~~MDEV-9216~~ [ ~~MDEV-9216~~ ]

Alexander Barkov made changes - 2015-12-01 10:50

Link

This issue is blocked by ~~MDEV-9217~~ [ ~~MDEV-9217~~ ]

Alexander Barkov made changes - 2015-12-01 11:10

Link

This issue is blocked by ~~MDEV-9218~~ [ ~~MDEV-9218~~ ]

Alexander Barkov made changes - 2015-12-01 11:43

Link

This issue is blocked by MDEV-9219 [ MDEV-9219 ]

Alexander Barkov made changes - 2015-12-01 11:50

Link

This issue is blocked by ~~MDEV-9220~~ [ ~~MDEV-9220~~ ]

Alexander Barkov made changes - 2015-12-01 12:33

Link

This issue is blocked by ~~MDEV-9221~~ [ ~~MDEV-9221~~ ]

Alexander Barkov made changes - 2015-12-03 07:44

Link

This issue is blocked by ~~MDEV-9234~~ [ ~~MDEV-9234~~ ]

Alexander Barkov made changes - 2015-12-03 07:51

Link

This issue is blocked by ~~MDEV-9235~~ [ ~~MDEV-9235~~ ]

Rasmus Johansson (Inactive) made changes - 2015-12-03 13:51

Sprint

10.2.0-1 [ 21 ]

10.2.0-1, 5.5.47-1 [ 21, 22 ]

Rasmus Johansson (Inactive) made changes - 2015-12-03 13:51

Rank

Ranked higher

Rasmus Johansson (Inactive) made changes - 2015-12-03 13:53

Sprint

10.2.0-1, 5.5.47-1 [ 21, 22 ]

10.2.0-1 [ 21 ]

Rasmus Johansson (Inactive) made changes - 2015-12-03 13:53

Rank

Ranked lower

Alexander Barkov made changes - 2015-12-04 11:38

Link

This issue is blocked by ~~MDEV-9238~~ [ ~~MDEV-9238~~ ]

Alexander Barkov made changes - 2015-12-23 10:31

Link

This issue is blocked by ~~MDEV-9316~~ [ ~~MDEV-9316~~ ]

Alexander Barkov made changes - 2015-12-24 11:03

Link

This issue is blocked by ~~MDEV-9319~~ [ ~~MDEV-9319~~ ]

Alexander Barkov made changes - 2015-12-26 19:21

Link

This issue is blocked by ~~MDEV-9326~~ [ ~~MDEV-9326~~ ]

Alexander Barkov made changes - 2015-12-26 21:17

Link

This issue is blocked by ~~MDEV-9327~~ [ ~~MDEV-9327~~ ]

Rasmus Johansson (Inactive) made changes - 2015-12-28 09:22

Sprint

10.2.0-1 [ 21 ]

10.2.0-1, 10.2.0-2 [ 21, 26 ]

Rasmus Johansson (Inactive) made changes - 2015-12-28 09:22

Rank

Ranked lower

Alexander Barkov made changes - 2015-12-28 13:10

Link

This issue is blocked by MDEV-9331 [ MDEV-9331 ]

Alexander Barkov made changes - 2015-12-28 14:22

Link

This issue is blocked by MDEV-9333 [ MDEV-9333 ]

Alexander Barkov made changes - 2015-12-28 17:18

Link

This issue is blocked by ~~MDEV-9334~~ [ ~~MDEV-9334~~ ]

Alexander Barkov made changes - 2015-12-28 18:31

Link

This issue is blocked by MDEV-9336 [ MDEV-9336 ]

Alexander Barkov made changes - 2015-12-28 18:38

Link

This issue is blocked by ~~MDEV-9337~~ [ ~~MDEV-9337~~ ]

Alexander Barkov made changes - 2015-12-29 14:15

Link

This issue is blocked by ~~MDEV-9340~~ [ ~~MDEV-9340~~ ]

Alexander Barkov made changes - 2015-12-30 09:11

Link

This issue is blocked by MDEV-9343 [ MDEV-9343 ]

Alexander Barkov made changes - 2015-12-30 10:38

Link

This issue is blocked by MDEV-9344 [ MDEV-9344 ]

Rasmus Johansson (Inactive) made changes - 2016-01-07 11:51

Rank

Ranked higher

Alexander Barkov made changes - 2016-01-11 08:38

Link

This issue is blocked by ~~MDEV-9391~~ [ ~~MDEV-9391~~ ]

Alexander Barkov made changes - 2016-01-11 09:34

Link

This issue is blocked by ~~MDEV-9392~~ [ ~~MDEV-9392~~ ]

Alexander Barkov made changes - 2016-01-11 11:25

Link

This issue is blocked by ~~MDEV-9393~~ [ ~~MDEV-9393~~ ]

Alexander Barkov made changes - 2016-01-11 16:01

Link

This issue is blocked by ~~MDEV-9395~~ [ ~~MDEV-9395~~ ]

Alexander Barkov made changes - 2016-01-11 16:09

Link

This issue is blocked by ~~MDEV-9396~~ [ ~~MDEV-9396~~ ]

Alexander Barkov made changes - 2016-01-11 16:11

Link

This issue is blocked by ~~MDEV-9397~~ [ ~~MDEV-9397~~ ]

Alexander Barkov made changes - 2016-01-11 16:27

Link

This issue is blocked by ~~MDEV-9398~~ [ ~~MDEV-9398~~ ]

Alexander Barkov made changes - 2016-01-13 07:39

Link

This issue is blocked by ~~MDEV-9405~~ [ ~~MDEV-9405~~ ]

Alexander Barkov made changes - 2016-01-13 08:52

Link

This issue is blocked by ~~MDEV-9406~~ [ ~~MDEV-9406~~ ]

Alexander Barkov made changes - 2016-01-13 10:37

Link

This issue is blocked by ~~MDEV-9407~~ [ ~~MDEV-9407~~ ]

Alexander Barkov made changes - 2016-01-13 11:16

Link

This issue is blocked by ~~MDEV-9408~~ [ ~~MDEV-9408~~ ]

Alexander Barkov made changes - 2016-01-13 14:18

Link

This issue is blocked by ~~MDEV-9410~~ [ ~~MDEV-9410~~ ]

Rasmus Johansson (Inactive) made changes - 2016-01-13 15:46

Sprint

10.2.0-1, 10.2.0-2 [ 21, 26 ]

10.2.0-1, 10.2.0-2, 10.2.0-4 [ 21, 26, 29 ]

Alexander Barkov made changes - 2016-01-14 10:22

Link

This issue relates to MDEV-9417 [ MDEV-9417 ]

Sergei Golubchik made changes - 2016-01-15 20:08

Link

This issue includes ~~MDEV-7199~~ [ ~~MDEV-7199~~ ]

Sergei Golubchik made changes - 2016-01-15 20:24

Link

This issue includes MDEV-8094 [ MDEV-8094 ]

Sergei Golubchik made changes - 2016-01-16 15:52

Link

This issue blocks ~~MDEV-9144~~ [ ~~MDEV-9144~~ ]

Alexander Barkov made changes - 2016-01-16 16:26

Link

This issue relates to MDEV-9425 [ MDEV-9425 ]

Rasmus Johansson (Inactive) made changes - 2016-01-21 12:00

Rank

Ranked higher

Alexander Barkov made changes - 2016-01-22 15:15

Link

This issue is blocked by MDEV-9452 [ MDEV-9452 ]

Rasmus Johansson (Inactive) made changes - 2016-01-27 11:23

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4 [ 21, 26, 29 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5 [ 21, 26, 29, 32 ]

Rasmus Johansson (Inactive) made changes - 2016-01-27 11:23

Rank

Ranked lower

Alexander Barkov made changes - 2016-01-30 20:32

Link

This issue is blocked by ~~MDEV-9495~~ [ ~~MDEV-9495~~ ]

Alexander Barkov made changes - 2016-01-30 22:15

Link

This issue is blocked by ~~MDEV-9497~~ [ ~~MDEV-9497~~ ]

Alexander Barkov made changes - 2016-02-05 15:26

Link

This issue is blocked by ~~MDEV-9522~~ [ ~~MDEV-9522~~ ]

Alexander Barkov made changes - 2016-02-05 15:34

Link

This issue is blocked by MDEV-9523 [ MDEV-9523 ]

Sergei Golubchik made changes - 2016-02-05 18:07

Link

This issue includes MDEV-9523 [ MDEV-9523 ]

Sergei Golubchik made changes - 2016-02-05 18:07

Link

This issue is blocked by MDEV-9523 [ MDEV-9523 ]

Sergei Golubchik made changes - 2016-02-05 18:08

Link

This issue includes ~~MDEV-9522~~ [ ~~MDEV-9522~~ ]

Sergei Golubchik made changes - 2016-02-05 18:08

Link

This issue is blocked by ~~MDEV-9522~~ [ ~~MDEV-9522~~ ]

Colin Charles made changes - 2016-02-18 12:03

Labels

gsoc14

gsoc14 gsoc16

Sergei Golubchik made changes - 2016-02-18 13:48

Labels

gsoc14 gsoc16

gsoc14

Alexander Barkov made changes - 2016-02-24 11:47

Assignee	Alexander Barkov [ bar ]	Sergei Golubchik [ serg ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Alexander Barkov made changes - 2016-02-24 11:48

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5 [ 21, 26, 29, 32 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6 [ 21, 26, 29, 32, 37 ]

Rasmus Johansson (Inactive) made changes - 2016-03-03 08:13

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6 [ 21, 26, 29, 32, 37 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7 [ 21, 26, 29, 32, 37, 39 ]

Rasmus Johansson (Inactive) made changes - 2016-03-03 08:13

Rank

Ranked lower

Rasmus Johansson (Inactive) made changes - 2016-03-09 13:07

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7 [ 21, 26, 29, 32, 37, 39 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8 [ 21, 26, 29, 32, 37, 39, 41 ]

Rasmus Johansson (Inactive) made changes - 2016-03-09 13:07

Rank

Ranked lower

Alexander Barkov made changes - 2016-03-10 05:15

Link

This issue is blocked by MDEV-9706 [ MDEV-9706 ]

Sergei Golubchik made changes - 2016-03-10 07:50

Link

This issue is blocked by MDEV-9706 [ MDEV-9706 ]

Sergei Golubchik made changes - 2016-03-10 07:51

Link

This issue relates to MDEV-9706 [ MDEV-9706 ]

Rasmus Johansson (Inactive) made changes - 2016-05-04 13:41

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8 [ 21, 26, 29, 32, 37, 39, 41 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1 [ 21, 26, 29, 32, 37, 39, 41, 56 ]

Rasmus Johansson (Inactive) made changes - 2016-05-04 13:41

Rank

Ranked higher

Rasmus Johansson (Inactive) made changes - 2016-05-11 07:08

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1 [ 21, 26, 29, 32, 37, 39, 41, 56 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-2 [ 21, 26, 29, 32, 37, 39, 41, 56, 63 ]

Rasmus Johansson (Inactive) made changes - 2016-05-18 09:27

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-2 [ 21, 26, 29, 32, 37, 39, 41, 56, 63 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3 [ 21, 26, 29, 32, 37, 39, 41, 56, 65 ]

Rasmus Johansson (Inactive) made changes - 2016-05-18 09:27

Rank

Ranked higher

Rasmus Johansson (Inactive) made changes - 2016-05-25 08:39

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3 [ 21, 26, 29, 32, 37, 39, 41, 56, 65 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66 ]

Rasmus Johansson (Inactive) made changes - 2016-06-01 08:05

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4, 10.2.1-5 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66, 68 ]

Rasmus Johansson (Inactive) made changes - 2016-07-27 12:10

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4, 10.2.1-5 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66, 68 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4, 10.2.1-5, 10.2.2-3 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66, 68, 83 ]

Rasmus Johansson (Inactive) made changes - 2016-07-27 12:10

Rank

Ranked lower

Sergei Golubchik made changes - 2016-10-09 11:21

Fix Version/s

10.2 [ 14601 ]

Alexander Barkov made changes - 2016-11-16 08:42

Link

This issue is blocked by ~~MDEV-10811~~ [ ~~MDEV-10811~~ ]

Alexander Barkov made changes - 2016-11-16 08:42

Link

This issue is blocked by ~~MDEV-11294~~ [ ~~MDEV-11294~~ ]

Alexander Barkov made changes - 2016-11-16 14:02

Link

This issue is blocked by ~~MDEV-11298~~ [ ~~MDEV-11298~~ ]

Alexander Barkov made changes - 2016-11-17 13:21

Link

This issue is blocked by ~~MDEV-11302~~ [ ~~MDEV-11302~~ ]

Alexander Barkov made changes - 2016-11-17 14:04

Link

This issue is blocked by MDEV-11304 [ MDEV-11304 ]

Alexander Barkov made changes - 2016-11-22 08:04

Link

This issue is blocked by ~~MDEV-11330~~ [ ~~MDEV-11330~~ ]

Alexander Barkov made changes - 2016-11-22 09:20

Link

This issue is blocked by ~~MDEV-11331~~ [ ~~MDEV-11331~~ ]

Alexander Barkov made changes - 2016-11-22 17:12

Link

This issue is blocked by ~~MDEV-11337~~ [ ~~MDEV-11337~~ ]

Alexander Barkov made changes - 2016-11-22 17:19

Link

This issue is blocked by ~~MDEV-11333~~ [ ~~MDEV-11333~~ ]

Alexander Barkov made changes - 2016-11-24 12:13

Link

This issue is blocked by ~~MDEV-11344~~ [ ~~MDEV-11344~~ ]

Alexander Barkov made changes - 2016-11-26 17:21

Link

This issue is blocked by ~~MDEV-11357~~ [ ~~MDEV-11357~~ ]

Alexander Barkov made changes - 2016-11-28 06:12

Link

This issue is blocked by ~~MDEV-11365~~ [ ~~MDEV-11365~~ ]

Alexander Barkov made changes - 2016-12-02 11:17

Link

This issue is blocked by MDEV-11458 [ MDEV-11458 ]

Alexander Barkov made changes - 2016-12-02 21:39

Link

This issue is blocked by ~~MDEV-11478~~ [ ~~MDEV-11478~~ ]

Alexander Barkov made changes - 2016-12-05 05:04

Link

This issue is blocked by ~~MDEV-11482~~ [ ~~MDEV-11482~~ ]

Alexander Barkov made changes - 2016-12-05 14:21

Link

This issue is blocked by ~~MDEV-11485~~ [ ~~MDEV-11485~~ ]

Alexander Barkov made changes - 2016-12-08 13:54

Link

This issue is blocked by ~~MDEV-11503~~ [ ~~MDEV-11503~~ ]

Alexander Barkov made changes - 2016-12-09 04:39

Link

This issue is blocked by MDEV-11511 [ MDEV-11511 ]

Alexander Barkov made changes - 2016-12-09 09:58

Link

This issue is blocked by ~~MDEV-11514~~ [ ~~MDEV-11514~~ ]

Alexander Barkov made changes - 2016-12-10 14:12

Link

This issue is blocked by ~~MDEV-11528~~ [ ~~MDEV-11528~~ ]

Alexander Barkov made changes - 2016-12-12 07:15

Link

This issue is blocked by ~~MDEV-11497~~ [ ~~MDEV-11497~~ ]

Alexander Barkov made changes - 2016-12-13 10:19

Link

This issue is blocked by ~~MDEV-11554~~ [ ~~MDEV-11554~~ ]

Alexander Barkov made changes - 2016-12-13 10:22

Link

This issue is blocked by ~~MDEV-11555~~ [ ~~MDEV-11555~~ ]

Alexander Barkov made changes - 2016-12-13 12:48

Link

This issue is blocked by ~~MDEV-11558~~ [ ~~MDEV-11558~~ ]

Alexander Barkov made changes - 2016-12-20 14:15

Link

This issue is blocked by ~~MDEV-11615~~ [ ~~MDEV-11615~~ ]

Alexander Barkov made changes - 2016-12-27 15:15

Link

This issue is blocked by ~~MDEV-11672~~ [ ~~MDEV-11672~~ ]

Alexander Barkov made changes - 2016-12-30 15:37

Link

This issue is blocked by ~~MDEV-11692~~ [ ~~MDEV-11692~~ ]

Alexander Barkov made changes - 2017-01-16 15:22

Link

This issue is blocked by ~~MDEV-11815~~ [ ~~MDEV-11815~~ ]

Alexander Barkov made changes - 2017-01-26 09:00

Link

This issue is blocked by ~~MDEV-11913~~ [ ~~MDEV-11913~~ ]

Alexander Barkov made changes - 2017-02-06 04:28

Link

This issue is blocked by ~~MDEV-12001~~ [ ~~MDEV-12001~~ ]

Alexander Barkov made changes - 2017-03-07 14:11

Link

This issue is blocked by ~~MDEV-12199~~ [ ~~MDEV-12199~~ ]

Alexander Barkov made changes - 2017-03-13 04:54

Assignee

Sergei Golubchik [ serg ]

Alexander Barkov [ bar ]

Alexander Barkov made changes - 2017-03-13 05:05

Link

This issue is blocked by ~~MDEV-12238~~ [ ~~MDEV-12238~~ ]

Alexander Barkov made changes - 2017-03-13 05:09

Link

This issue is blocked by ~~MDEV-12239~~ [ ~~MDEV-12239~~ ]

Alexander Barkov made changes - 2017-03-16 16:11

Link

This issue blocks MDEV-10593 [ MDEV-10593 ]

Alexander Barkov made changes - 2017-03-20 07:45

Link

This issue is blocked by ~~MDEV-12303~~ [ ~~MDEV-12303~~ ]

Alexander Barkov made changes - 2017-03-22 04:42

Link

This issue is blocked by ~~MDEV-12325~~ [ ~~MDEV-12325~~ ]

Alexander Barkov made changes - 2017-03-23 07:56

Link

This issue is blocked by ~~MDEV-12338~~ [ ~~MDEV-12338~~ ]

Alexander Barkov made changes - 2017-04-02 11:56

Link

This issue is blocked by ~~MDEV-12426~~ [ ~~MDEV-12426~~ ]

Alexander Barkov made changes - 2017-04-09 05:18

Link

This issue is blocked by ~~MDEV-11245~~ [ ~~MDEV-11245~~ ]

Alexander Barkov made changes - 2017-04-09 05:20

Link

This issue is blocked by ~~MDEV-9522~~ [ ~~MDEV-9522~~ ]

Alexander Barkov made changes - 2017-04-09 05:20

Link

This issue includes ~~MDEV-9522~~ [ ~~MDEV-9522~~ ]

Alexander Barkov made changes - 2017-04-09 05:21

Link

This issue is blocked by ~~MDEV-7199~~ [ ~~MDEV-7199~~ ]

Alexander Barkov made changes - 2017-04-09 05:21

Link

This issue includes ~~MDEV-7199~~ [ ~~MDEV-7199~~ ]

Alexander Barkov made changes - 2017-04-09 05:21

Link

This issue is blocked by MDEV-9523 [ MDEV-9523 ]

Alexander Barkov made changes - 2017-04-09 05:21

Link

This issue includes MDEV-9523 [ MDEV-9523 ]

Alexander Barkov made changes - 2017-04-09 05:22

Link

This issue is blocked by MDEV-8094 [ MDEV-8094 ]

Alexander Barkov made changes - 2017-04-09 05:22

Link

This issue includes MDEV-8094 [ MDEV-8094 ]

Alexander Barkov made changes - 2017-04-09 05:22

Status

In Review [ 10002 ]

Stalled [ 10000 ]

Alexander Barkov made changes - 2017-04-09 05:22

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Alexander Barkov made changes - 2017-04-13 08:27

Link

This issue is blocked by ~~MDEV-12497~~ [ ~~MDEV-12497~~ ]

Alexander Barkov made changes - 2017-04-14 10:39

Link

This issue is blocked by ~~MDEV-12505~~ [ ~~MDEV-12505~~ ]

Alexander Barkov made changes - 2017-04-14 10:39

Link

This issue is blocked by ~~MDEV-12504~~ [ ~~MDEV-12504~~ ]

Alexander Barkov made changes - 2017-04-14 10:40

Link

This issue is blocked by MDEV-12503 [ MDEV-12503 ]

Alexander Barkov made changes - 2017-04-14 18:38

Link

This issue is blocked by ~~MDEV-12506~~ [ ~~MDEV-12506~~ ]

Alexander Barkov made changes - 2017-04-15 02:51

Link

This issue is blocked by ~~MDEV-12505~~ [ ~~MDEV-12505~~ ]

Alexander Barkov made changes - 2017-04-17 05:05

Link

This issue is blocked by MDEV-5402 [ MDEV-5402 ]

Alexander Barkov made changes - 2017-04-17 05:06

Link

This issue is blocked by MDEV-4654 [ MDEV-4654 ]

Alexander Barkov made changes - 2017-04-17 05:08

Link

This issue is blocked by ~~MDEV-8911~~ [ ~~MDEV-8911~~ ]

Alexander Barkov made changes - 2017-04-17 05:09

Link

This issue is blocked by MDEV-5895 [ MDEV-5895 ]

Alexander Barkov made changes - 2017-04-17 05:13

Link

This issue is blocked by MDEV-7928 [ MDEV-7928 ]

Alexander Barkov made changes - 2017-04-17 05:14

Link

This issue is blocked by MDEV-10902 [ MDEV-10902 ]

Alexander Barkov made changes - 2017-04-17 05:16

Link

This issue is blocked by MDEV-9541 [ MDEV-9541 ]

Alexander Barkov made changes - 2017-04-17 05:18

Link

This issue is blocked by MDEV-12513 [ MDEV-12513 ]

Alexander Barkov made changes - 2017-04-17 06:28

Link

This issue is blocked by ~~MDEV-12514~~ [ ~~MDEV-12514~~ ]

Alexander Barkov made changes - 2017-04-21 10:11

Link

This issue is blocked by ~~MDEV-12546~~ [ ~~MDEV-12546~~ ]

Alexander Barkov made changes - 2017-04-22 16:52

Link

This issue is blocked by ~~MDEV-12559~~ [ ~~MDEV-12559~~ ]

Alexander Barkov made changes - 2017-04-22 18:19

Link

This issue is blocked by ~~MDEV-12560~~ [ ~~MDEV-12560~~ ]

Alexander Barkov made changes - 2017-04-23 12:31

Link

This issue is blocked by MDEV-12565 [ MDEV-12565 ]

Alexander Barkov made changes - 2017-04-23 12:32

Link

This issue is blocked by MDEV-12566 [ MDEV-12566 ]

Alexander Barkov made changes - 2017-04-23 12:33

Link

This issue is blocked by MDEV-12567 [ MDEV-12567 ]

Alexander Barkov made changes - 2017-04-23 16:51

Link

This issue is blocked by ~~MDEV-12568~~ [ ~~MDEV-12568~~ ]

Alexander Barkov made changes - 2017-04-24 11:46

Link

This issue is blocked by ~~MDEV-12574~~ [ ~~MDEV-12574~~ ]

Alexander Barkov made changes - 2017-04-25 04:40

Link

This issue is blocked by ~~MDEV-12582~~ [ ~~MDEV-12582~~ ]

Alexander Barkov made changes - 2017-04-25 14:43

Link

This issue is blocked by ~~MDEV-12588~~ [ ~~MDEV-12588~~ ]

Alexander Barkov made changes - 2017-04-27 05:33

Link

This issue is blocked by ~~MDEV-12594~~ [ ~~MDEV-12594~~ ]

Alexander Barkov made changes - 2017-04-27 05:52

Link

This issue is blocked by ~~MDEV-12595~~ [ ~~MDEV-12595~~ ]

Alexander Barkov made changes - 2017-04-27 10:08

Link

This issue is blocked by ~~MDEV-12599~~ [ ~~MDEV-12599~~ ]

Alexander Barkov made changes - 2017-04-27 11:17

Link

This issue is blocked by ~~MDEV-12601~~ [ ~~MDEV-12601~~ ]

Alexander Barkov made changes - 2017-04-27 16:33

Link

This issue is blocked by ~~MDEV-12607~~ [ ~~MDEV-12607~~ ]

Alexander Barkov made changes - 2017-04-28 03:48

Link

This issue is blocked by MDEV-12613 [ MDEV-12613 ]

Alexander Barkov made changes - 2017-04-28 09:02

Link

This issue is blocked by ~~MDEV-12617~~ [ ~~MDEV-12617~~ ]

Alexander Barkov made changes - 2017-04-28 11:18

Link

This issue is blocked by ~~MDEV-12619~~ [ ~~MDEV-12619~~ ]

Alexander Barkov made changes - 2017-04-30 18:29

Link

This issue is blocked by ~~MDEV-12649~~ [ ~~MDEV-12649~~ ]

Alexander Barkov made changes - 2017-05-02 03:42

Link

This issue is blocked by ~~MDEV-12655~~ [ ~~MDEV-12655~~ ]

Alexander Barkov made changes - 2017-05-02 14:31

Link

This issue is blocked by ~~MDEV-12665~~ [ ~~MDEV-12665~~ ]

Alexander Barkov made changes - 2017-05-02 17:56

Link

This issue is blocked by ~~MDEV-12668~~ [ ~~MDEV-12668~~ ]

Alexander Barkov made changes - 2017-05-04 11:31

Link

This issue is blocked by ~~MDEV-12687~~ [ ~~MDEV-12687~~ ]

Alexander Barkov made changes - 2017-05-04 13:48

Link

This issue is blocked by ~~MDEV-12691~~ [ ~~MDEV-12691~~ ]

Alexander Barkov made changes - 2017-05-04 14:14

Link

This issue is blocked by ~~MDEV-12692~~ [ ~~MDEV-12692~~ ]

Alexander Barkov made changes - 2017-05-05 02:59

Link

This issue is blocked by ~~MDEV-12695~~ [ ~~MDEV-12695~~ ]

Alexander Barkov made changes - 2017-05-05 19:21

Link

This issue is blocked by ~~MDEV-12707~~ [ ~~MDEV-12707~~ ]

Alexander Barkov made changes - 2017-05-06 06:38

Link

This issue is blocked by ~~MDEV-12710~~ [ ~~MDEV-12710~~ ]

Alexander Barkov made changes - 2017-05-06 13:04

Link

This issue is blocked by MDEV-12712 [ MDEV-12712 ]

Alexander Barkov made changes - 2017-05-06 15:10

Link

This issue is blocked by ~~MDEV-12713~~ [ ~~MDEV-12713~~ ]

Alexander Barkov made changes - 2017-05-06 16:41

Link

This issue is blocked by ~~MDEV-12714~~ [ ~~MDEV-12714~~ ]

Alexander Barkov made changes - 2017-05-06 19:02

Link

This issue is blocked by ~~MDEV-12716~~ [ ~~MDEV-12716~~ ]

Alexander Barkov made changes - 2017-05-06 21:01

Link

This issue is blocked by ~~MDEV-12717~~ [ ~~MDEV-12717~~ ]

Alexander Barkov made changes - 2017-05-07 04:48

Link

This issue is blocked by ~~MDEV-12718~~ [ ~~MDEV-12718~~ ]

Alexander Barkov made changes - 2017-05-07 04:50

Link

This issue is blocked by ~~MDEV-12719~~ [ ~~MDEV-12719~~ ]

Alexander Barkov made changes - 2017-05-07 12:24

Link

This issue is blocked by ~~MDEV-12721~~ [ ~~MDEV-12721~~ ]

Alexander Barkov made changes - 2017-05-10 03:32

Link

This issue is blocked by ~~MDEV-12769~~ [ ~~MDEV-12769~~ ]

Alexander Barkov made changes - 2017-05-10 03:35

Link

This issue is blocked by ~~MDEV-12770~~ [ ~~MDEV-12770~~ ]

Alexander Barkov made changes - 2017-05-10 06:23

Link

This issue is blocked by ~~MDEV-12772~~ [ ~~MDEV-12772~~ ]

Alexander Barkov made changes - 2017-05-10 10:47

Link

This issue is blocked by ~~MDEV-12775~~ [ ~~MDEV-12775~~ ]

Alexander Barkov made changes - 2017-05-10 13:15

Link

This issue is blocked by ~~MDEV-12777~~ [ ~~MDEV-12777~~ ]

Daniel Black made changes - 2017-05-13 05:34

Link

This issue is duplicated by MDEV-12786 [ MDEV-12786 ]

Alexander Barkov made changes - 2017-05-15 09:11

Link

This issue is blocked by ~~MDEV-12798~~ [ ~~MDEV-12798~~ ]

Alexander Barkov made changes - 2017-05-15 12:53

Link

This issue is blocked by ~~MDEV-12803~~ [ ~~MDEV-12803~~ ]

Alexander Barkov made changes - 2017-05-16 03:50

Link

This issue is blocked by ~~MDEV-12809~~ [ ~~MDEV-12809~~ ]

Alexander Barkov made changes - 2017-05-17 10:00

Link

This issue is blocked by ~~MDEV-12826~~ [ ~~MDEV-12826~~ ]

Alexander Barkov made changes - 2017-05-17 12:09

Link

This issue is blocked by MDEV-12828 [ MDEV-12828 ]

Alexander Barkov made changes - 2017-05-17 12:15

Link

This issue is blocked by ~~MDEV-12829~~ [ ~~MDEV-12829~~ ]

Alexander Barkov made changes - 2017-05-17 12:16

Link

This issue is blocked by ~~MDEV-12830~~ [ ~~MDEV-12830~~ ]

Alexander Barkov made changes - 2017-05-17 12:23

Link

This issue is blocked by ~~MDEV-12831~~ [ ~~MDEV-12831~~ ]

Alexander Barkov made changes - 2017-05-17 13:51

Link

This issue is blocked by ~~MDEV-12833~~ [ ~~MDEV-12833~~ ]

Alexander Barkov made changes - 2017-05-19 14:02

Link

This issue is blocked by ~~MDEV-12849~~ [ ~~MDEV-12849~~ ]

Alexander Barkov made changes - 2017-05-19 18:16

Link

This issue is blocked by ~~MDEV-12853~~ [ ~~MDEV-12853~~ ]

Alexander Barkov made changes - 2017-05-20 11:03

Link

This issue is blocked by ~~MDEV-12854~~ [ ~~MDEV-12854~~ ]

Alexander Barkov made changes - 2017-05-21 04:01

Link

This issue is blocked by ~~MDEV-12856~~ [ ~~MDEV-12856~~ ]

Alexander Barkov made changes - 2017-05-21 04:06

Link

This issue is blocked by ~~MDEV-12857~~ [ ~~MDEV-12857~~ ]

Alexander Barkov made changes - 2017-05-22 04:44

Link

This issue is blocked by ~~MDEV-12860~~ [ ~~MDEV-12860~~ ]

Alexander Barkov made changes - 2017-05-22 05:26

Link

This issue is blocked by ~~MDEV-12858~~ [ ~~MDEV-12858~~ ]

Alexander Barkov made changes - 2017-05-22 05:26

Link

This issue is blocked by ~~MDEV-12859~~ [ ~~MDEV-12859~~ ]

Alexander Barkov made changes - 2017-05-22 06:25

Link

This issue is blocked by ~~MDEV-12861~~ [ ~~MDEV-12861~~ ]

Alexander Barkov made changes - 2017-05-22 07:33

Link

This issue is blocked by ~~MDEV-12862~~ [ ~~MDEV-12862~~ ]

Alexander Barkov made changes - 2017-05-22 11:29

Link

This issue is blocked by ~~MDEV-12866~~ [ ~~MDEV-12866~~ ]

Alexander Barkov made changes - 2017-05-23 14:37

Link

This issue is blocked by ~~MDEV-12876~~ [ ~~MDEV-12876~~ ]

Sergei Golubchik made changes - 2017-05-24 10:47

Link

This issue blocks MDEV-12786 [ MDEV-12786 ]

Sergei Golubchik made changes - 2017-05-24 10:47

Link

This issue is duplicated by MDEV-12786 [ MDEV-12786 ]

Alexander Barkov made changes - 2017-05-24 12:37

Link

This issue blocks MDEV-11058 [ MDEV-11058 ]

Alexander Barkov made changes - 2017-05-24 12:37

Link

This issue blocks ~~MDEV-12252~~ [ ~~MDEV-12252~~ ]

Alexander Barkov made changes - 2017-05-24 12:37

Link

This issue blocks MDEV-10592 [ MDEV-10592 ]

Alexander Barkov made changes - 2017-05-24 12:38

Link

This issue blocks MDEV-10575 [ MDEV-10575 ]

Alexander Barkov made changes - 2017-05-24 12:38

Link

This issue blocks MDEV-12307 [ MDEV-12307 ]

Alexander Barkov made changes - 2017-05-24 12:38

Link

This issue blocks MDEV-12308 [ MDEV-12308 ]

Rasmus Johansson (Inactive) made changes - 2017-05-24 13:20

Sprint

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4, 10.2.1-5, 10.2.2-3 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66, 68, 83 ]

10.2.0-1, 10.2.0-2, 10.2.0-4, 10.2.0-5, 10.2.0-6, 10.2.0-7, 10.2.0-8, 10.2.1-1, 10.2.1-3, 10.2.1-4, 10.2.1-5, 10.2.2-3, 10.3.1-1 [ 21, 26, 29, 32, 37, 39, 41, 56, 65, 66, 68, 83, 164 ]

Alexander Barkov made changes - 2017-05-25 08:57

Link

This issue is blocked by ~~MDEV-12916~~ [ ~~MDEV-12916~~ ]

Alexander Barkov made changes - 2017-05-25 10:02

Link

This issue is blocked by ~~MDEV-12917~~ [ ~~MDEV-12917~~ ]

Alexander Barkov made changes - 2017-05-26 15:23

Link

This issue is blocked by MDEV-12927 [ MDEV-12927 ]

Alexander Barkov made changes - 2017-05-27 07:07

Link

This issue is blocked by ~~MDEV-12932~~ [ ~~MDEV-12932~~ ]

Alexander Barkov made changes - 2017-05-27 08:30

Link

This issue is blocked by ~~MDEV-10309~~ [ ~~MDEV-10309~~ ]

Sergei Golubchik made changes - 2017-05-29 20:00

Link

This issue relates to ~~MDEV-9056~~ [ ~~MDEV-9056~~ ]

Sergei Golubchik made changes - 2017-07-05 15:18

Link

This issue blocks ~~MDEV-9144~~ [ ~~MDEV-9144~~ ]

Alexander Barkov made changes - 2017-08-15 04:38

Link

This issue is blocked by ~~MDEV-13526~~ [ ~~MDEV-13526~~ ]

Alexander Barkov made changes - 2017-09-29 12:18

Link

This issue is blocked by ~~MDEV-13964~~ [ ~~MDEV-13964~~ ]

Alexander Barkov made changes - 2017-09-29 17:22

Link

This issue is blocked by ~~MDEV-13965~~ [ ~~MDEV-13965~~ ]

Alexander Barkov made changes - 2017-09-29 20:54

Link

This issue is blocked by ~~MDEV-13966~~ [ ~~MDEV-13966~~ ]

Alexander Barkov made changes - 2017-09-30 09:20

Link

This issue is blocked by ~~MDEV-13967~~ [ ~~MDEV-13967~~ ]

Alexander Barkov made changes - 2017-10-04 10:14

Link

This issue is blocked by ~~MDEV-13995~~ [ ~~MDEV-13995~~ ]

Alexander Barkov made changes - 2017-10-04 10:19

Link

This issue is blocked by ~~MDEV-13997~~ [ ~~MDEV-13997~~ ]

Alexander Barkov made changes - 2017-10-06 16:48

Link

This issue relates to MDEV-8284 [ MDEV-8284 ]

Alexander Barkov made changes - 2017-10-06 16:54

Link

This issue relates to MDEV-11361 [ MDEV-11361 ]

Alexander Barkov made changes - 2017-10-06 16:55

Link

This issue relates to ~~MDEV-11362~~ [ ~~MDEV-11362~~ ]

Alexander Barkov made changes - 2017-11-21 05:22

Link

This issue is blocked by ~~MDEV-14454~~ [ ~~MDEV-14454~~ ]

Alexander Barkov made changes - 2017-11-22 11:38

Link

This issue is blocked by ~~MDEV-14467~~ [ ~~MDEV-14467~~ ]

Alexander Barkov made changes - 2017-11-24 07:59

Link

This issue is blocked by ~~MDEV-14494~~ [ ~~MDEV-14494~~ ]

Alexander Barkov made changes - 2017-12-12 11:40

Link

This issue is blocked by ~~MDEV-14630~~ [ ~~MDEV-14630~~ ]

Alexander Barkov made changes - 2017-12-15 11:37

Link

This issue is blocked by MDEV-14661 [ MDEV-14661 ]

Alexander Barkov made changes - 2018-01-10 11:43

Link

This issue is blocked by MDEV-14910 [ MDEV-14910 ]

Alexander Barkov made changes - 2018-02-04 17:43

Link

This issue is blocked by ~~MDEV-15205~~ [ ~~MDEV-15205~~ ]

Alexander Barkov made changes - 2018-02-13 04:54

Link

This issue blocks ~~MDEV-15293~~ [ ~~MDEV-15293~~ ]

Alexander Barkov made changes - 2018-02-13 04:54

Link

This issue blocks ~~MDEV-15293~~ [ ~~MDEV-15293~~ ]

Alexander Barkov made changes - 2018-02-13 04:55

Link

This issue is blocked by ~~MDEV-15293~~ [ ~~MDEV-15293~~ ]

Alexander Barkov made changes - 2018-02-14 05:24

Link

This issue is blocked by MDEV-15310 [ MDEV-15310 ]

Alexander Barkov made changes - 2018-02-17 06:43

Link

This issue is blocked by ~~MDEV-15340~~ [ ~~MDEV-15340~~ ]

Alexander Barkov made changes - 2018-02-20 15:10

Link

This issue blocks ~~MDEV-15363~~ [ ~~MDEV-15363~~ ]

Alexander Barkov made changes - 2018-02-20 15:10

Link

This issue blocks ~~MDEV-15363~~ [ ~~MDEV-15363~~ ]

Alexander Barkov made changes - 2018-02-20 15:10

Link

This issue is blocked by ~~MDEV-15363~~ [ ~~MDEV-15363~~ ]

Alexander Barkov made changes - 2018-02-24 13:59

Link

This issue is blocked by ~~MDEV-15406~~ [ ~~MDEV-15406~~ ]

Alexander Barkov made changes - 2018-03-19 12:50

Link

This issue is blocked by ~~MDEV-15597~~ [ ~~MDEV-15597~~ ]

Alexander Barkov made changes - 2018-03-27 11:06

Link

This issue is blocked by ~~MDEV-15689~~ [ ~~MDEV-15689~~ ]

Alexander Barkov made changes - 2018-03-28 06:10

Link

This issue is blocked by ~~MDEV-15702~~ [ ~~MDEV-15702~~ ]

Alexander Barkov made changes - 2018-03-28 08:04

Link

This issue is blocked by MDEV-15704 [ MDEV-15704 ]

Alexander Barkov made changes - 2018-03-29 05:58

Link

This issue is blocked by ~~MDEV-15714~~ [ ~~MDEV-15714~~ ]

Alexander Barkov made changes - 2018-04-03 08:42

Link

This issue is blocked by ~~MDEV-15758~~ [ ~~MDEV-15758~~ ]

Alexander Barkov made changes - 2018-04-10 08:37

Link

This issue is blocked by ~~MDEV-15834~~ [ ~~MDEV-15834~~ ]

Alexander Barkov made changes - 2018-04-19 06:30

Link

This issue is blocked by ~~MDEV-15926~~ [ ~~MDEV-15926~~ ]

Alexander Barkov made changes - 2018-04-19 06:31

Link

This issue is blocked by MDEV-15927 [ MDEV-15927 ]

Alexander Barkov made changes - 2018-04-19 09:03

Link

This issue relates to MDEV-15924 [ MDEV-15924 ]

Alexander Barkov made changes - 2018-04-19 09:07

Link

This issue is blocked by MDEV-15901 [ MDEV-15901 ]

Alexander Barkov made changes - 2018-04-19 09:12

Link

This issue is blocked by MDEV-15930 [ MDEV-15930 ]

Alexander Barkov made changes - 2018-04-20 10:51

Link

This issue is blocked by ~~MDEV-15946~~ [ ~~MDEV-15946~~ ]

Alexander Barkov made changes - 2018-04-21 15:34

Link

This issue is blocked by ~~MDEV-15957~~ [ ~~MDEV-15957~~ ]

Alexander Barkov made changes - 2018-04-21 18:33

Link

This issue is blocked by ~~MDEV-15960~~ [ ~~MDEV-15960~~ ]

Alexander Barkov made changes - 2018-04-22 08:28

Link

This issue relates to ~~MDEV-15971~~ [ ~~MDEV-15971~~ ]

Alexander Barkov made changes - 2018-04-22 08:28

Link

This issue relates to ~~MDEV-15971~~ [ ~~MDEV-15971~~ ]

Alexander Barkov made changes - 2018-04-22 08:28

Link

This issue is blocked by ~~MDEV-15971~~ [ ~~MDEV-15971~~ ]

Alexander Barkov made changes - 2018-05-24 05:13

Link

This issue is blocked by ~~MDEV-16280~~ [ ~~MDEV-16280~~ ]

Alexander Barkov made changes - 2018-05-28 08:57

Link

This issue is blocked by ~~MDEV-16309~~ [ ~~MDEV-16309~~ ]

Alexander Barkov made changes - 2018-05-29 12:13

Link

This issue is blocked by ~~MDEV-16320~~ [ ~~MDEV-16320~~ ]

Alexander Barkov made changes - 2018-05-29 12:14

Link

This issue is blocked by ~~MDEV-16316~~ [ ~~MDEV-16316~~ ]

Alexander Barkov made changes - 2018-05-30 02:19

Link

This issue is blocked by MDEV-16324 [ MDEV-16324 ]

Alexander Barkov made changes - 2018-05-30 05:10

Link

This issue is blocked by MDEV-16325 [ MDEV-16325 ]

Alexander Barkov made changes - 2018-05-31 09:46

Link

This issue is blocked by ~~MDEV-16351~~ [ ~~MDEV-16351~~ ]

Alexander Barkov made changes - 2018-06-01 17:44

Link

This issue is blocked by MDEV-16373 [ MDEV-16373 ]

Alexander Barkov made changes - 2018-06-04 05:05

Link

This issue is blocked by ~~MDEV-16379~~ [ ~~MDEV-16379~~ ]

Alexander Barkov made changes - 2018-06-04 12:16

Link

This issue is blocked by ~~MDEV-16385~~ [ ~~MDEV-16385~~ ]

Alexander Barkov made changes - 2018-06-04 13:30

Link

This issue is blocked by ~~MDEV-16388~~ [ ~~MDEV-16388~~ ]

Alexander Barkov made changes - 2018-06-06 10:59

Link

This issue is blocked by ~~MDEV-16414~~ [ ~~MDEV-16414~~ ]

Alexander Barkov made changes - 2018-06-06 13:26

Link

This issue blocks MDEV-11829 [ MDEV-11829 ]

Alexander Barkov made changes - 2018-06-07 19:15

Link

This issue is blocked by ~~MDEV-16426~~ [ ~~MDEV-16426~~ ]

Alexander Barkov made changes - 2018-06-09 09:23

Link

This issue is blocked by ~~MDEV-16451~~ [ ~~MDEV-16451~~ ]

Alexander Barkov made changes - 2018-06-09 09:35

Link

This issue is blocked by ~~MDEV-16452~~ [ ~~MDEV-16452~~ ]

Alexander Barkov made changes - 2018-06-10 03:33

Link

This issue is blocked by ~~MDEV-16454~~ [ ~~MDEV-16454~~ ]

Alexander Barkov made changes - 2018-07-24 07:47

Link

This issue is blocked by ~~MDEV-16806~~ [ ~~MDEV-16806~~ ]

Alexander Barkov made changes - 2018-07-24 12:50

Link

This issue is blocked by ~~MDEV-16814~~ [ ~~MDEV-16814~~ ]

Alexander Barkov made changes - 2018-07-25 08:34

Link

This issue is blocked by ~~MDEV-16823~~ [ ~~MDEV-16823~~ ]

Alexander Barkov made changes - 2018-07-30 12:08

Link

This issue is blocked by ~~MDEV-16852~~ [ ~~MDEV-16852~~ ]

Alexander Barkov made changes - 2018-07-31 04:10

Link

This issue is blocked by ~~MDEV-16861~~ [ ~~MDEV-16861~~ ]

Alexander Barkov made changes - 2018-07-31 12:55

Link

This issue is blocked by ~~MDEV-16864~~ [ ~~MDEV-16864~~ ]

Alexander Barkov made changes - 2018-08-01 12:08

Link

This issue is blocked by ~~MDEV-16874~~ [ ~~MDEV-16874~~ ]

Alexander Barkov made changes - 2018-08-02 11:35

Link

This issue is blocked by ~~MDEV-16881~~ [ ~~MDEV-16881~~ ]

Alexander Barkov made changes - 2018-08-02 13:48

Link

This issue is blocked by ~~MDEV-16884~~ [ ~~MDEV-16884~~ ]

Alexander Barkov made changes - 2018-08-03 03:54

Link

This issue is blocked by ~~MDEV-16888~~ [ ~~MDEV-16888~~ ]

Alexander Barkov made changes - 2018-08-09 04:28

Link

This issue is blocked by ~~MDEV-16926~~ [ ~~MDEV-16926~~ ]

Alexander Barkov made changes - 2018-08-11 10:30

Link

This issue is blocked by ~~MDEV-16939~~ [ ~~MDEV-16939~~ ]

Alexander Barkov made changes - 2018-09-18 16:42

Link

This issue blocks MDEV-10018 [ MDEV-10018 ]

Alexander Barkov made changes - 2018-09-18 16:48

Link

This issue is blocked by MDEV-12513 [ MDEV-12513 ]

Alexander Barkov made changes - 2018-09-18 16:49

Link

This issue blocks MDEV-12513 [ MDEV-12513 ]

Alexander Barkov made changes - 2018-09-28 19:04

Link

This issue is blocked by ~~MDEV-17325~~ [ ~~MDEV-17325~~ ]

Alexander Barkov made changes - 2018-09-30 12:02

Link

This issue is blocked by MDEV-17329 [ MDEV-17329 ]

Alexander Barkov made changes - 2018-09-30 13:15

Link

This issue is blocked by ~~MDEV-17330~~ [ ~~MDEV-17330~~ ]

Alexander Barkov made changes - 2018-10-01 15:42

Link

This issue is blocked by MDEV-17335 [ MDEV-17335 ]

Alexander Barkov made changes - 2018-10-07 11:04

Link

This issue is blocked by MDEV-17384 [ MDEV-17384 ]

Alexander Barkov made changes - 2018-10-15 06:04

Link

This issue is blocked by MDEV-8490 [ MDEV-8490 ]

Alexander Barkov made changes - 2018-10-15 06:10

Link

This issue is blocked by MDEV-8515 [ MDEV-8515 ]

Alexander Barkov made changes - 2018-10-25 19:49

Link

This issue relates to ~~MDEV-16443~~ [ ~~MDEV-16443~~ ]

Alexander Barkov made changes - 2018-11-06 11:23

Link

This issue is blocked by ~~MDEV-17625~~ [ ~~MDEV-17625~~ ]

Alexander Barkov made changes - 2018-11-07 06:07

Link

This issue is blocked by MDEV-17632 [ MDEV-17632 ]

Alexander Barkov made changes - 2018-12-03 07:37

Link

This issue is blocked by MDEV-7063 [ MDEV-7063 ]

Alexander Barkov made changes - 2018-12-05 04:17

Link

This issue is blocked by ~~MDEV-17905~~ [ ~~MDEV-17905~~ ]

Alexander Barkov made changes - 2019-04-01 16:12

Link

This issue is blocked by ~~MDEV-19125~~ [ ~~MDEV-19125~~ ]

Alexander Barkov made changes - 2019-04-05 08:18

Link

This issue is blocked by MDEV-19180 [ MDEV-19180 ]

Alexander Barkov made changes - 2019-04-06 03:33

Link

This issue is blocked by MDEV-19196 [ MDEV-19196 ]

Alexander Barkov made changes - 2019-04-06 07:37

Link

This issue is blocked by ~~MDEV-19197~~ [ ~~MDEV-19197~~ ]

Alexander Barkov made changes - 2019-04-23 07:34

Link

This issue is blocked by MDEV-9706 [ MDEV-9706 ]

Alexander Barkov made changes - 2019-04-23 07:35

Link

This issue relates to MDEV-9706 [ MDEV-9706 ]

Alexander Barkov made changes - 2019-04-23 08:29

Link

This issue is blocked by ~~MDEV-19311~~ [ ~~MDEV-19311~~ ]

Alexander Barkov made changes - 2019-04-24 06:28

Link

This issue is blocked by ~~MDEV-19317~~ [ ~~MDEV-19317~~ ]

Alexander Barkov made changes - 2019-04-26 10:45

Link

This issue is blocked by ~~MDEV-19345~~ [ ~~MDEV-19345~~ ]

Alexander Barkov made changes - 2019-05-01 04:46

Link

This issue is blocked by ~~MDEV-19377~~ [ ~~MDEV-19377~~ ]

Alexander Barkov made changes - 2019-05-22 12:02

Link

This issue is blocked by ~~MDEV-19550~~ [ ~~MDEV-19550~~ ]

Alexander Barkov made changes - 2019-05-23 10:36

Link

This issue is blocked by ~~MDEV-19566~~ [ ~~MDEV-19566~~ ]

Alexander Barkov made changes - 2019-05-25 07:39

Link

This issue is blocked by ~~MDEV-19593~~ [ ~~MDEV-19593~~ ]

Alexander Barkov made changes - 2019-05-28 02:46

Link

This issue is blocked by ~~MDEV-19612~~ [ ~~MDEV-19612~~ ]

Alexander Barkov made changes - 2019-06-04 07:57

Link

This issue is blocked by ~~MDEV-19686~~ [ ~~MDEV-19686~~ ]

Alexander Barkov made changes - 2019-06-07 03:25

Link

This issue is blocked by MDEV-19708 [ MDEV-19708 ]

Alexander Barkov made changes - 2019-06-07 08:45

Link

This issue is blocked by ~~MDEV-19710~~ [ ~~MDEV-19710~~ ]

Alexander Barkov made changes - 2019-06-10 09:58

Link

This issue is blocked by ~~MDEV-19724~~ [ ~~MDEV-19724~~ ]

Alexander Barkov made changes - 2019-06-11 02:26

Link

This issue is blocked by ~~MDEV-19727~~ [ ~~MDEV-19727~~ ]

Alexander Barkov made changes - 2019-06-16 03:24

Link

This issue is blocked by ~~MDEV-19772~~ [ ~~MDEV-19772~~ ]

Alexander Barkov made changes - 2019-06-20 01:48

Link

This issue is blocked by ~~MDEV-19810~~ [ ~~MDEV-19810~~ ]

Alexander Barkov made changes - 2019-06-21 02:42

Link

This issue is blocked by ~~MDEV-19818~~ [ ~~MDEV-19818~~ ]

Alexander Barkov made changes - 2019-06-24 02:23

Link

This issue is blocked by ~~MDEV-19843~~ [ ~~MDEV-19843~~ ]

Alexander Barkov made changes - 2019-06-27 12:21

Link

This issue is blocked by ~~MDEV-19888~~ [ ~~MDEV-19888~~ ]

Alexander Barkov made changes - 2019-06-29 05:45

Link

This issue is blocked by ~~MDEV-19908~~ [ ~~MDEV-19908~~ ]

Alexander Barkov made changes - 2019-07-02 06:42

Link

This issue is blocked by ~~MDEV-19923~~ [ ~~MDEV-19923~~ ]

Alexander Barkov made changes - 2019-07-02 12:22

Link

This issue relates to MDEV-19927 [ MDEV-19927 ]

Alexander Barkov made changes - 2019-07-03 15:11

Link

This issue is blocked by ~~MDEV-19944~~ [ ~~MDEV-19944~~ ]

Alexander Barkov made changes - 2019-07-05 02:02

Link

This issue is blocked by ~~MDEV-19957~~ [ ~~MDEV-19957~~ ]

Alexander Barkov made changes - 2019-07-05 16:51

Link

This issue is blocked by ~~MDEV-19972~~ [ ~~MDEV-19972~~ ]

Alexander Barkov made changes - 2019-07-09 02:26

Link

This issue is blocked by ~~MDEV-19991~~ [ ~~MDEV-19991~~ ]

Alexander Barkov made changes - 2019-07-09 08:41

Link

This issue is blocked by ~~MDEV-19994~~ [ ~~MDEV-19994~~ ]

Alexander Barkov made changes - 2019-07-10 03:12

Link

This issue is blocked by ~~MDEV-20006~~ [ ~~MDEV-20006~~ ]

Alexander Barkov made changes - 2019-07-10 07:49

Link

This issue is blocked by ~~MDEV-20009~~ [ ~~MDEV-20009~~ ]

Alexander Barkov made changes - 2019-07-10 14:44

Link

This issue is blocked by ~~MDEV-20016~~ [ ~~MDEV-20016~~ ]

Alexander Barkov made changes - 2019-07-11 08:26

Link

This issue is blocked by ~~MDEV-20042~~ [ ~~MDEV-20042~~ ]

Alexander Barkov made changes - 2019-07-12 02:55

Link

This issue is blocked by ~~MDEV-20052~~ [ ~~MDEV-20052~~ ]

Alexander Barkov made changes - 2019-07-25 10:45

Link

This issue is blocked by ~~MDEV-20175~~ [ ~~MDEV-20175~~ ]

Alexander Barkov made changes - 2019-08-12 11:24

Link

This issue is blocked by ~~MDEV-20326~~ [ ~~MDEV-20326~~ ]

Alexander Barkov made changes - 2019-08-12 18:13

Link

This issue is blocked by ~~MDEV-20332~~ [ ~~MDEV-20332~~ ]

Julien Fritsch made changes - 2019-08-13 13:53

Issue Type

Task [ 3 ]

Epic [ 5 ]

Alexander Barkov made changes - 2019-08-14 05:49

Link

This issue is blocked by ~~MDEV-20342~~ [ ~~MDEV-20342~~ ]

Alexander Barkov made changes - 2019-08-14 05:52

Fix Version/s

10.5 [ 23123 ]

Alexander Barkov made changes - 2019-08-14 08:05

Link

This issue is blocked by MDEV-20343 [ MDEV-20343 ]

Alexander Barkov made changes - 2019-08-15 05:26

Link

This issue is blocked by ~~MDEV-20351~~ [ ~~MDEV-20351~~ ]

Alexander Barkov made changes - 2019-08-15 08:12

Link

This issue is blocked by ~~MDEV-20353~~ [ ~~MDEV-20353~~ ]

Alexander Barkov made changes - 2019-09-26 07:06

Link

This issue is blocked by ~~MDEV-20674~~ [ ~~MDEV-20674~~ ]

Alexander Barkov made changes - 2019-09-29 17:54

Link

This issue is blocked by ~~MDEV-20696~~ [ ~~MDEV-20696~~ ]

Alexander Barkov made changes - 2019-10-01 01:20

Link

This issue is blocked by ~~MDEV-20704~~ [ ~~MDEV-20704~~ ]

Alexander Barkov made changes - 2019-10-01 09:11

Link

This issue is blocked by ~~MDEV-20706~~ [ ~~MDEV-20706~~ ]

Alexander Barkov made changes - 2019-10-01 11:33

Link

This issue is blocked by ~~MDEV-20708~~ [ ~~MDEV-20708~~ ]

Alexander Barkov made changes - 2019-10-01 13:16

Link

This issue is blocked by ~~MDEV-20711~~ [ ~~MDEV-20711~~ ]

Alexander Barkov made changes - 2019-10-01 14:47

Link

This issue is blocked by ~~MDEV-20712~~ [ ~~MDEV-20712~~ ]

Alexander Barkov made changes - 2019-10-01 19:33

Link

This issue is blocked by ~~MDEV-20716~~ [ ~~MDEV-20716~~ ]

Alexander Barkov made changes - 2019-10-02 06:40

Link

This issue is blocked by ~~MDEV-20721~~ [ ~~MDEV-20721~~ ]

Max Mether made changes - 2019-10-02 15:12

Link

This issue blocks MENT-412 [ MENT-412 ]

Alexander Barkov made changes - 2019-10-03 09:12

Link

This issue is blocked by ~~MDEV-20734~~ [ ~~MDEV-20734~~ ]

Alexander Barkov made changes - 2019-10-05 14:04

Link

This issue is blocked by ~~MDEV-20760~~ [ ~~MDEV-20760~~ ]

Alexander Barkov made changes - 2019-10-07 07:30

Link

This issue is blocked by ~~MDEV-20764~~ [ ~~MDEV-20764~~ ]

Alexander Barkov made changes - 2019-10-15 13:43

Link

This issue is blocked by ~~MDEV-20831~~ [ ~~MDEV-20831~~ ]

Alexander Barkov made changes - 2019-10-16 09:16

Link

This issue is blocked by ~~MDEV-20837~~ [ ~~MDEV-20837~~ ]

Julien Fritsch made changes - 2019-11-14 09:20

Epic Name

Add a plugin to field types (column types)

Julien Fritsch made changes - 2019-11-18 11:27

Summary

Add a plugin to field types (column types)

Data type plugin API version 1

Julien Fritsch made changes - 2019-11-18 11:45

Link

This issue is blocked by MDEV-8515 [ MDEV-8515 ]

Julien Fritsch made changes - 2019-11-18 11:45

Link

This issue is blocked by MDEV-9336 [ MDEV-9336 ]

Julien Fritsch made changes - 2019-11-18 11:51

Link

This issue is blocked by MDEV-9343 [ MDEV-9343 ]

Julien Fritsch made changes - 2019-11-18 11:51

Link

This issue is blocked by MDEV-9344 [ MDEV-9344 ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by ~~MDEV-9405~~ [ ~~MDEV-9405~~ ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by MDEV-9452 [ MDEV-9452 ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by MDEV-9541 [ MDEV-9541 ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by MDEV-10902 [ MDEV-10902 ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by MDEV-11304 [ MDEV-11304 ]

Julien Fritsch made changes - 2019-11-18 11:52

Link

This issue is blocked by MDEV-11458 [ MDEV-11458 ]

Julien Fritsch made changes - 2019-11-18 11:53

Link

This issue is blocked by MDEV-11511 [ MDEV-11511 ]

Julien Fritsch made changes - 2019-11-18 11:53

Link

This issue is blocked by ~~MDEV-12325~~ [ ~~MDEV-12325~~ ]

Julien Fritsch made changes - 2019-11-18 11:53

Link

This issue is blocked by MDEV-12503 [ MDEV-12503 ]

Julien Fritsch made changes - 2019-11-18 11:53

Link

This issue is blocked by MDEV-12613 [ MDEV-12613 ]

Julien Fritsch made changes - 2019-11-18 11:53

Link

This issue is blocked by ~~MDEV-12668~~ [ ~~MDEV-12668~~ ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by ~~MDEV-12691~~ [ ~~MDEV-12691~~ ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by MDEV-12712 [ MDEV-12712 ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by MDEV-12828 [ MDEV-12828 ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by ~~MDEV-12829~~ [ ~~MDEV-12829~~ ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by ~~MDEV-12830~~ [ ~~MDEV-12830~~ ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by ~~MDEV-12831~~ [ ~~MDEV-12831~~ ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by MDEV-14661 [ MDEV-14661 ]

Julien Fritsch made changes - 2019-11-18 11:54

Link

This issue is blocked by MDEV-14910 [ MDEV-14910 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-15310 [ MDEV-15310 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-15704 [ MDEV-15704 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-15901 [ MDEV-15901 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-15927 [ MDEV-15927 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-15930 [ MDEV-15930 ]

Julien Fritsch made changes - 2019-11-18 11:55

Link

This issue is blocked by MDEV-16324 [ MDEV-16324 ]

Julien Fritsch made changes - 2019-11-18 11:56

Link

This issue is blocked by MDEV-16325 [ MDEV-16325 ]

Julien Fritsch made changes - 2019-11-18 11:56

Link

This issue is blocked by MDEV-19708 [ MDEV-19708 ]

Julien Fritsch made changes - 2019-11-18 11:57

Link

This issue is blocked by ~~MDEV-20711~~ [ ~~MDEV-20711~~ ]

Julien Fritsch made changes - 2019-11-18 11:57

Link

This issue is blocked by MDEV-19180 [ MDEV-19180 ]

Julien Fritsch made changes - 2019-11-18 11:57

Link

This issue is blocked by MDEV-17632 [ MDEV-17632 ]

Julien Fritsch made changes - 2019-11-18 11:57

Link

This issue is blocked by MDEV-17335 [ MDEV-17335 ]