| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Merge 10.4 into 10.5 | Marko Mäkelä | 2020-10-30 | 1 | -0/+1 |
| |\ | |||||
| | * | Merge 10.3 into 10.4 | Marko Mäkelä | 2020-10-29 | 1 | -0/+1 |
| | |\ | |||||
| | | * | Merge 10.2 into 10.3 | Marko Mäkelä | 2020-10-28 | 1 | -0/+1 |
| | | | | |||||
| * | | | MDEV-23437 Item_func_json_objectagg::print is not implemented. | Alexey Botchkov | 2020-10-24 | 1 | -0/+4 |
| | | | | | | | | | | | | | Fix the Item_func_json_objectagg::fix_fields to save the orig_args. | ||||
| * | | | Merge 10.4 into 10.5 | Marko Mäkelä | 2020-07-02 | 1 | -0/+13 |
| |\ \ \ | |/ / | |||||
| | * | | Merge 10.3 into 10.4 | Marko Mäkelä | 2020-07-02 | 1 | -0/+13 |
| | |\ \ | | |/ | |||||
| | | * | Merge 10.2 into 10.3 | Marko Mäkelä | 2020-07-02 | 1 | -0/+13 |
| | | | | |||||
| * | | | Make the test func_json deterministic | Varun Gupta | 2020-06-30 | 1 | -2/+2 |
| | | | | |||||
| * | | | MDEV-23029: JSON_OBJECTAGG returns NULL when used together with GROUP BY | Varun Gupta | 2020-06-29 | 1 | -0/+12 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Quick grouping is not supported for JSON_OBJECTAGG. The same for GROUP_CONCAT too so make sure that Item::quick_group is set to FALSE. We need to make sure that in the case of JSON_OBJECTAGG we don't create an index over grouping fields of the temp table and update the result after each iteration. Instead we should first sort the result in accordance to the GROUP BY fields and then perform the grouping and write the result to the temp table. | ||||
| * | | | MDEV-22837 JSON_ARRAYAGG and JSON_OBJECTAGG treat JSON arguments as text. | Alexey Botchkov | 2020-06-15 | 1 | -0/+6 |
| | | | | | | | | | | | | | Item_field::is_json_value() implemented. | ||||
| * | | | MDEV-22844 JSON_ARRAYAGG is limited by group_concat_max_len. | Alexey Botchkov | 2020-06-15 | 1 | -0/+8 |
| | | | | | | | | | | | | | Warning message and function result fixed | ||||
| * | | | MDEV-22840: JSON_ARRAYAGG gives wrong results with NULL values and ORDER by ↵ | Varun Gupta | 2020-06-12 | 1 | -0/+18 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | clause The problem here is similar to the case with DISTINCT, the tree used for ORDER BY needs to also hold the null bytes of the record. This was not done for GROUP_CONCAT as NULLS are rejected by GROUP_CONCAT. Also introduced a comparator function for the order by tree to handle null values with JSON_ARRAYAGG. | ||||
| * | | | MDEV-22011: DISTINCT with JSON_ARRAYAGG gives wrong results | Varun Gupta | 2020-06-12 | 1 | -0/+31 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For DISTINCT to be handled with JSON_ARRAYAGG, we need to make sure that the Unique tree also holds the NULL bytes of a table record inside the node of the tree. This behaviour for JSON_ARRAYAGG is different from GROUP_CONCAT because in GROUP_CONCAT we just reject NULL values for columns. Also introduced a comparator function for the unique tree to handle null values for distinct inside JSON_ARRAYAGG. | ||||
| * | | | MDEV-21902 Nested JSON_ARRAYAGG in JSON_OBJECT should not get escaped. | Alexey Botchkov | 2020-06-04 | 1 | -0/+2 |
| | | | | |||||
| * | | | MDEV-21914 JSON_ARRAYAGG doesn't reject ORDER BY clause, but doesn't work ↵ | Alexey Botchkov | 2020-06-04 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | | | either. ORDER BY fixed for JSON_ARRAYAGG. | ||||
| * | | | MDEV-22084 Squared brackets missing from JSON_ARRAYAGG when used in a view. | Alexey Botchkov | 2020-06-04 | 1 | -0/+4 |
| | | | | | | | | | | | | | | | | Item_func_groupconcat::print() should be fixed to work for the derived classes. | ||||
| * | | | MDEV-22640, MDEV-22449, MDEV-21528 JSON_ARRAYAGG crashes with NULL values. | Alexey Botchkov | 2020-06-04 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | | | | | We have to include NULL in the result which the GOUP_CONCAT doesn't always do. Also converting should be done into another String instance as these can be same. | ||||
| * | | | MDEV-21915 Server crashes in copy_fields,Item_func_group_concat::add … | Alexey Botchkov | 2020-04-29 | 1 | -0/+16 |
| | | | | | | | | | | | | | | | | | | | | | | …while using json_arrayagg() as a window function. We don't support JSON_ARRAYAGG and JSON_OBJECTAGG in window functions yet. | ||||
| * | | | MDEV-22236 JSON_ARRAYAGG query leads to SIGSEGV in Charset::swap on ↵ | Alexey Botchkov | 2020-04-28 | 1 | -0/+8 |
| | | | | | | | | | | | | | | | | | | | optimized builds. The json_arrayagg::val_str should handle NULL result. | ||||
| * | | | MDEV-16620 JSON_ARRAYAGG and JSON_OBJECTAGG. | Alexey Botchkov | 2019-10-14 | 1 | -1/+12 |
| | | | | | | | | | | | | | Ison_objectagg implemented. | ||||
| * | | | Merge branch 'MDEV-16620' of https://github.com/markus456/server into bb-10.5-hf | Alexey Botchkov | 2019-10-10 | 1 | -0/+90 |
| |\ \ \ | |/ / |/| | | | | | | | | Conflicts: sql/sql_yacc.yy | ||||
| | * | | MDEV-16620: Add JSON_ARRAYAGG function | Markus Mäkelä | 2019-07-04 | 1 | -0/+90 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The JSON_ARRAYAGG function extends the GROUP_CONCAT function and provides a method of aggregating JSON results. The current implementation supports DISTINCT and LIMIT but not ORDER BY (Oracle supports GROUP BY). Adding GROUP BY support is possible but it requires some extra work as the grouping appears to be done inside a temporary table that complicates matters. Added test cases that covert aggregation of all JSON types and JSON validation for the generated results. | ||||
| * | | | Merge remote-tracking branch 'origin/10.3' into 10.4 | Alexander Barkov | 2019-10-01 | 1 | -0/+10 |
| |\ \ \ | | |/ | |/| | |||||
| | * | | MDEV-19628 JSON with starting double quotes key is not valid. | Alexey Botchkov | 2019-09-30 | 1 | -0/+10 |
| | | | | | | | | | | | | | | | | First character of the key name is just skipped, so the escapement wasn't handled properly. | ||||
| * | | | Merge 10.3 into 10.4 | Marko Mäkelä | 2019-09-12 | 1 | -0/+7 |
| |\ \ \ | |/ / | |||||
| | * | | MDEV-19670 json escaped unicode parse error. | Alexey Botchkov | 2019-09-12 | 1 | -0/+7 |
| | | | | | | | | | | | | | Fixed 4-byte length characters handled incorrectly. | ||||
| * | | | Merge branch '10.3' into 10.4 | Sergei Golubchik | 2019-09-06 | 1 | -2/+5 |
| |\ \ \ | |/ / | | / | |/ |/| | |||||
| | * | Merge branch '10.2' into 10.3 | Monty | 2019-09-03 | 1 | -2/+5 |
| | | | |||||
| * | | Merge branch '10.3' into 10.4 | Oleksandr Byelkin | 2019-05-19 | 1 | -0/+43 |
| |\ \ | |/ | |||||
| | * | Merge branch '10.2' into 10.3 | Sergei Golubchik | 2019-05-17 | 1 | -0/+43 |
| | | | |||||
| * | | Merge 10.3 into 10.4 | Marko Mäkelä | 2019-03-12 | 1 | -0/+7 |
| |\ \ | |/ | |||||
| | * | Merge 10.2 into 10.3 | Marko Mäkelä | 2019-03-12 | 1 | -0/+7 |
| | | | |||||
| * | | Merge 10.3 into 10.4 | Marko Mäkelä | 2018-11-19 | 1 | -0/+18 |
| |\ \ | |/ | |||||
| | * | Merge 10.2 into 10.3 | Marko Mäkelä | 2018-11-19 | 1 | -0/+18 |
| | | | |||||
| * | | Merge 10.3 into 10.4 | Marko Mäkelä | 2018-10-05 | 1 | -0/+20 |
| |\ \ | |/ | |||||
| | * | Merge branch '10.2' into 10.3 | Sergei Golubchik | 2018-09-28 | 1 | -0/+20 |
| | | | |||||
| * | | Merge 10.3 into 10.4 | Marko Mäkelä | 2018-08-16 | 1 | -0/+24 |
| |\ \ | |/ | |||||
| | * | Merge branch '10.2' into 10.3 | Sergei Golubchik | 2018-08-12 | 1 | -0/+18 |
| | | | |||||
| | * | Merge 10.2 into 10.3 | Marko Mäkelä | 2018-08-03 | 1 | -0/+6 |
| | | | |||||
| * | | Merge remote-tracking branch 'origin/10.3' into 10.4 | Alexander Barkov | 2018-07-25 | 1 | -0/+10 |
| |\ \ | |/ | |||||
| | * | Merge remote-tracking branch 'origin/10.2' into 10.3 | Alexander Barkov | 2018-07-24 | 1 | -0/+10 |
| | | | |||||
| * | | Merge remote-tracking branch 'origin/10.3' into 10.4 | Alexander Barkov | 2018-07-03 | 1 | -0/+15 |
| |\ \ | |/ | |||||
| | * | Merge branch '10.2' into 10.3 | Sergei Golubchik | 2018-06-30 | 1 | -0/+15 |
| | | | |||||
| * | | MDEV-16351 JSON_OBJECT() treats hybrid functions with boolean arguments as ↵ | Alexander Barkov | 2018-05-31 | 1 | -0/+50 |
| |/ | | | | | | | | numbers Now the boolean data type is preserved in hybrid functions and MIN/MAX, so COALESCE(bool_expr,bool_expr) and MAX(bool_expr) are correctly detected by JSON_OBJECT() as being boolean rather than numeric expressions. | ||||
| * | Create 'main' test directory and move 't' and 'r' there | Michael Widenius | 2018-03-29 | 1 | -0/+426 |
 |
index : delta/mariadb-git.git | |
| github.com: MariaDB/server.git |
| summaryrefslogtreecommitdiff |