[MDEV-6274] Collation usage statistics - Jira

Alexander Barkov created issue - 2014-05-27 14:34

Alexander Barkov made changes - 2014-05-29 08:18

Field	Original Value	New Value
Description	Feedback plugin will include collation usage statistics. Every collation that has been used by the server will have a record in "SELECT * FROM information_schema.feedback" output, like this: {noformat} +----------------------------------------+---------------------+ \| VARIABLE_NAME \| VARIABLE_VALUE \| +----------------------------------------+---------------------+ \| Collation_utf8_unicode_ci::use_count \| 10 \| \| Collation_latin1_general_ci::use_count \| 20 \| +----------------------------------------+---------------------+ {noformat} The collation that have not been used will be included into the result. We'll also intorduce a new function COLLATIONPROPERTY (inspired by SQL Server): {noformat} SELECT COLLATIONPROPERTY(collation_name_or_id, property); {noformat} For example: {noformat} SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USE_COUNT'); SELECT COLLATIONPROPERTY(10, 'USE_COUNT'); {noformat} The function COLLATIONPROPERTY will be always available, even if the FEEDBACK plugin is not installed. The result type of the function will be "TEXT CHARACTER SET utf8". If the data type of the first argument (collation_name_or_id) is INTEGER, the argument will be treated as a collation ID. For the other data type the first argument will be treated as a collation name. Collation names will be case insensitive. Collation properties will be case insensitive. We'll support the following properties at this point: USE_COUNT - number of times a collation was accessed. TAILORING - collation tailoring rules for UCA collations, NULL otherwise (usefull for test purposes). If an unknown collation or an unknown property are passed to the function, NULL will be returned. We'll support more collation properties in the future, such as case sensitivity, accent sensitivity, Unicode version, etc.	Feedback plugin will include collation usage statistics. Every collation that has been used by the server will have a record in "SELECT * FROM information_schema.feedback" output, like this: {noformat} +----------------------------------------+---------------------+ \| VARIABLE_NAME \| VARIABLE_VALUE \| +----------------------------------------+---------------------+ \| Collation_usecount utf8_unicode_ci \| 10 \| \| Collation_usecount latin1_general_ci \| 20 \| +----------------------------------------+---------------------+ {noformat} The collation that have not been used will be included into the result. We'll also intorduce a new function COLLATIONPROPERTY (inspired by SQL Server): {noformat} SELECT COLLATIONPROPERTY(collation_name_or_id, property); {noformat} For example: {noformat} SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USE_COUNT'); SELECT COLLATIONPROPERTY(10, 'USE_COUNT'); {noformat} The function COLLATIONPROPERTY will be always available, even if the FEEDBACK plugin is not installed. The result type of the function will be "TEXT CHARACTER SET utf8". If the data type of the first argument (collation_name_or_id) is INTEGER, the argument will be treated as a collation ID. For the other data type the first argument will be treated as a collation name. Collation names will be case insensitive. Collation properties will be case insensitive. We'll support the following properties at this point: USE_COUNT - number of times a collation was accessed. TAILORING - collation tailoring rules for UCA collations, NULL otherwise (usefull for test purposes). If an unknown collation or an unknown property are passed to the function, NULL will be returned. We'll support more collation properties in the future, such as case sensitivity, accent sensitivity, Unicode version, etc.

Alexander Barkov made changes - 2014-05-29 08:19

Description

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation_usecount utf8_unicode_ci | 10 |
| Collation_usecount latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will be included into the result.

We'll also intorduce a new function COLLATIONPROPERTY
(inspired by SQL Server):

{noformat}
SELECT COLLATIONPROPERTY(collation_name_or_id, property);
{noformat}

For example:

{noformat}
SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USE_COUNT');
SELECT COLLATIONPROPERTY(10, 'USE_COUNT');
{noformat}

The function COLLATIONPROPERTY will be always available,
even if the FEEDBACK plugin is not installed.

The result type of the function will be "TEXT CHARACTER SET utf8".

If the data type of the first argument (collation_name_or_id) is INTEGER,
the argument will be treated as a collation ID. For the other data type
the first argument will be treated as a collation name.

Collation names will be case insensitive.
Collation properties will be case insensitive.

We'll support the following properties at this point:
USE_COUNT - number of times a collation was accessed.
TAILORING - collation tailoring rules for UCA collations, NULL otherwise
(usefull for test purposes).

If an unknown collation or an unknown property are passed to the function,
NULL will be returned.

We'll support more collation properties in the future,
such as case sensitivity, accent sensitivity, Unicode version, etc.

Alexander Barkov made changes - 2014-05-29 08:19

Description

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation_usecount utf8_unicode_ci | 10 |
| Collation_usecount latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will be included into the result.

We'll also intorduce a new function COLLATIONPROPERTY
(inspired by SQL Server):

{noformat}
SELECT COLLATIONPROPERTY(collation_name_or_id, property);
{noformat}

For example:

{noformat}
SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USE_COUNT');
SELECT COLLATIONPROPERTY(10, 'USE_COUNT');
{noformat}

The function COLLATIONPROPERTY will be always available,
even if the FEEDBACK plugin is not installed.

The result type of the function will be "TEXT CHARACTER SET utf8".

If the data type of the first argument (collation_name_or_id) is INTEGER,
the argument will be treated as a collation ID. For the other data type
the first argument will be treated as a collation name.

Collation names will be case insensitive.
Collation properties will be case insensitive.

We'll support the following properties at this point:
USE_COUNT - number of times a collation was accessed.
TAILORING - collation tailoring rules for UCA collations, NULL otherwise
(usefull for test purposes).

If an unknown collation or an unknown property are passed to the function,
NULL will be returned.

We'll support more collation properties in the future,
such as case sensitivity, accent sensitivity, Unicode version, etc.

Alexander Barkov made changes - 2014-05-29 08:20

Description

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation_usecount utf8_unicode_ci | 10 |
| Collation_usecount latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will be included into the result.

We'll also intorduce a new function COLLATIONPROPERTY
(inspired by SQL Server):

{noformat}
SELECT COLLATIONPROPERTY(collation_name_or_id, property);
{noformat}

For example:

{noformat}
SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USE_COUNT');
SELECT COLLATIONPROPERTY(10, 'USE_COUNT');
{noformat}

The function COLLATIONPROPERTY will be always available,
even if the FEEDBACK plugin is not installed.

The result type of the function will be "TEXT CHARACTER SET utf8".

If the data type of the first argument (collation_name_or_id) is INTEGER,
the argument will be treated as a collation ID. For the other data type
the first argument will be treated as a collation name.

Collation names will be case insensitive.
Collation properties will be case insensitive.

We'll support the following properties at this point:
USE_COUNT - number of times a collation was accessed.
TAILORING - collation tailoring rules for UCA collations, NULL otherwise
(usefull for test purposes).

If an unknown collation or an unknown property are passed to the function,
NULL will be returned.

We'll support more collation properties in the future,
such as case sensitivity, accent sensitivity, Unicode version, etc.

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation_usecount utf8_unicode_ci | 10 |
| Collation_usecount latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will be included into the result.

We'll also intorduce a new function COLLATIONPROPERTY
(inspired by SQL Server):

{noformat}
SELECT COLLATIONPROPERTY(collation_name_or_id, property);
{noformat}

For example:

{noformat}
SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USECOUNT');
SELECT COLLATIONPROPERTY(10, 'USECOUNT');
{noformat}

The function COLLATIONPROPERTY will be always available,
even if the FEEDBACK plugin is not installed.

The result type of the function will be "TEXT CHARACTER SET utf8".

If the data type of the first argument (collation_name_or_id) is numeric,
the argument will be treated as a collation ID. For string data types
the first argument will be treated as a collation name.

Collation names will be case insensitive.
Collation properties will be case insensitive.

We'll support the following properties at this point:
USECOUNT - number of times a collation was accessed.
TAILORING - collation tailoring rules for UCA collations, NULL otherwise
(usefull for test purposes).

If an unknown collation or an unknown property are passed to the function,
NULL will be returned with a warning.

We'll support more collation properties in the future,
such as case sensitivity, accent sensitivity, Unicode version, etc.

Sergei Golubchik made changes - 2014-05-29 18:27

Assignee

Alexander Barkov [ bar ]

Sergei Golubchik [ serg ]

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

Workflow

defaullt [ 41400 ]

MariaDB v2 [ 42941 ]

Sergei Golubchik made changes - 2014-06-22 20:15

Status

Open [ 1 ]

In Review [ 10002 ]

Sergei Golubchik made changes - 2014-06-24 17:49

Fix Version/s		10.0.13 [ 16300 ]
Fix Version/s	10.0 [ 16000 ]

Sergei Golubchik made changes - 2014-07-03 12:48

Assignee	Sergei Golubchik [ serg ]	Alexander Barkov [ bar ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Sergei Golubchik made changes - 2014-07-29 23:55

Assignee

Alexander Barkov [ bar ]

Sergei Golubchik [ serg ]

Sergei Golubchik made changes - 2014-07-29 23:55

Status

Stalled [ 10000 ]

In Review [ 10002 ]

Sergei Golubchik made changes - 2014-07-30 14:42

Assignee	Sergei Golubchik [ serg ]	Alexander Barkov [ bar ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Alexander Barkov made changes - 2014-08-11 04:56

Description

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation_usecount utf8_unicode_ci | 10 |
| Collation_usecount latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will be included into the result.

We'll also intorduce a new function COLLATIONPROPERTY
(inspired by SQL Server):

{noformat}
SELECT COLLATIONPROPERTY(collation_name_or_id, property);
{noformat}

For example:

{noformat}
SELECT COLLATIONPROPERTY('utf8_unicode_ci', 'USECOUNT');
SELECT COLLATIONPROPERTY(10, 'USECOUNT');
{noformat}

The function COLLATIONPROPERTY will be always available,
even if the FEEDBACK plugin is not installed.

The result type of the function will be "TEXT CHARACTER SET utf8".

If the data type of the first argument (collation_name_or_id) is numeric,
the argument will be treated as a collation ID. For string data types
the first argument will be treated as a collation name.

Collation names will be case insensitive.
Collation properties will be case insensitive.

We'll support the following properties at this point:
USECOUNT - number of times a collation was accessed.
TAILORING - collation tailoring rules for UCA collations, NULL otherwise
(usefull for test purposes).

If an unknown collation or an unknown property are passed to the function,
NULL will be returned with a warning.

We'll support more collation properties in the future,
such as case sensitivity, accent sensitivity, Unicode version, etc.

Feedback plugin will include collation usage statistics.
Every collation that has been used by the server
will have a record in "SELECT * FROM information_schema.feedback"
output, like this:

{noformat}
+----------------------------------------+---------------------+
| VARIABLE_NAME | VARIABLE_VALUE |
+----------------------------------------+---------------------+
| Collation used utf8_unicode_ci | 10 |
| Collation used latin1_general_ci | 20 |
+----------------------------------------+---------------------+
{noformat}

The collation that have not been used will not be included into the result.

Sergei Golubchik made changes - 2014-08-12 16:03

Fix Version/s		10.0.14 [ 17101 ]
Fix Version/s	10.0.13 [ 16300 ]

Sergei Golubchik made changes - 2014-08-12 16:35

Fix Version/s		10.0 [ 16000 ]
Fix Version/s	10.0.14 [ 17101 ]

Alexander Barkov made changes - 2014-08-27 06:22

Link

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

Alexander Barkov added a comment - 2014-08-27 07:01

Pushed into 10.0.14

Alexander Barkov added a comment - 2014-08-27 07:01 Pushed into 10.0.14

Alexander Barkov made changes - 2014-08-27 07:01

Fix Version/s		10.0.14 [ 17101 ]
Fix Version/s	10.0 [ 16000 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

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

Workflow

MariaDB v2 [ 42941 ]

MariaDB v3 [ 64579 ]

Sergei Golubchik made changes - 2021-12-06 21:22

Workflow

MariaDB v3 [ 64579 ]

MariaDB v4 [ 132344 ]

MariaDB Server

Collation usage statistics

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration