Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
12.0.0
-
None
Description
In the following test case, the DISTINCT flag isn't handled properly, resulting in the mysqltest_tmp_v view generating non-distinct values:
CREATE TABLE simple_table ( running_number INTEGER NOT NULL AUTO_INCREMENT ,
|
geo GEOMETRY, PRIMARY KEY ( RUNNING_NUMBER));
|
INSERT INTO simple_table ( geo) VALUES
|
(ST_GEOMFROMTEXT('GEOMETRYCOLLECTION EMPTY')),
|
(ST_GEOMFROMTEXT('GEOMETRYCOLLECTION EMPTY'));
|
 |
CREATE OR REPLACE VIEW mysqltest_tmp_v AS SELECT ST_ASTEXT(ST_COLLECT(DISTINCT geo) OVER( ORDER BY running_number ROWS BETWEEN 1 PRECEDING AND CURRENT ROW)) AS geocollect FROM simple_table;
|
If we query with the SELECT directly, as given below, then the correct query result is given:
SELECT ST_ASTEXT(ST_COLLECT(DISTINCT geo) OVER( ORDER BY running_number ROWS BETWEEN 1 PRECEDING AND CURRENT ROW)) AS geocollect FROM simple_table;
|
Attachments
Issue Links
- causes
-
MDEV-36694 main.spatial_utility_function_collect broken for --view-protocol
-
- Closed
-