Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serialization Error occurs when using Disjoint #204

Closed
cuteDen-ECNU opened this issue Dec 6, 2023 · 2 comments · Fixed by #226
Closed

Serialization Error occurs when using Disjoint #204

cuteDen-ECNU opened this issue Dec 6, 2023 · 2 comments · Fixed by #226

Comments

@cuteDen-ECNU
Copy link

The following statement triggers an internal error:

DROP TABLE IF EXISTS origin; 
CREATE TABLE origin (id int, geom geometry);
INSERT INTO origin (id, geom) VALUES (0, ST_Boundary(ST_GeomFromText('GEOMETRYCOLLECTION EMPTY')));
INSERT INTO origin (id, geom) VALUES (1, ST_Boundary(ST_GeomFromText('MULTILINESTRING((7 33,4 31 ,9 31 ,13 27 ,7 33))')));
SELECT  ST_Disjoint(a1.geom, a2.geom) FROM origin as a1, origin as a2 WHERE a1.id = 1 and a2.id = 0;
--Error: near line 5: Serialization Error: Trying to read past end of buffer

Meanwhile, there is an empty result when querying the Disjoint directly as following statement:

SELECT ST_Disjoint(a1, a2) FROM
(SELECT ST_Boundary(ST_GeomFromText('GEOMETRYCOLLECTION EMPTY')) As a1
, ST_CollectionExtract(ST_Boundary(ST_GeomFromText('MULTILINESTRING((7 33,4 31 ,9 31 ,13 27 ,7 33))'))) As a2) As subquery;
-- ┌─────────────────────┐
-- │ st_disjoint(a1, a2) │
-- │       boolean       │
-- ├─────────────────────┤
-- │                     │
-- └─────────────────────┘

Version:
Spatial version:
FORCE INSTALL spatial FROM 'http://nightly-extensions.duckdb.org'; and LOAD spatial;
DuchDB version;
[('v0.9.2', '3c695d7ba9')]

@cuteDen-ECNU
Copy link
Author

@Maxxen, did you already have a chance to look at the report? After this is being fixed, we could continue finding and reporting additional potential bugs.

@Maxxen
Copy link
Member

Maxxen commented Dec 31, 2023

Will look into this after the holidays!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants