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

LINESTRING EMPTY crashes duckdb spatial. #27

Open
cuteDen-ECNU opened this issue Nov 24, 2023 · 1 comment
Open

LINESTRING EMPTY crashes duckdb spatial. #27

cuteDen-ECNU opened this issue Nov 24, 2023 · 1 comment

Comments

@cuteDen-ECNU
Copy link
Owner

cuteDen-ECNU commented Nov 24, 2023

Hi, the following statement crashes duckdb spatial.

SELECT ST_PointOnSurface(ST_Collect([ST_GeomFromText('LINESTRING(0 0, 1 1)'), ST_GeomFromText('LINESTRING EMPTY')]))
--Segmentation fault (core dumped)

Using the function ST_AsText, I got the following result.

SELECT ST_AsText(ST_Collect([ST_GeomFromText('LINESTRING(0 0, 1 1)'), ST_GeomFromText('LINESTRING EMPTY')]))
-- [('MULTILINESTRING ((0 0, 1 1), ())',)]

Version:

The result of "pragma version;" is [('v0.9.2', '3c695d7ba9')]

I used "FORCE INSTALL spatial FROM 'http://nightly-extensions.duckdb.org';" in the Python client.

@cuteDen-ECNU cuteDen-ECNU changed the title LINESTRING EMPTY crashes duchdb spatial. LINESTRING EMPTY crashes duckdb spatial. Nov 24, 2023
@cuteDen-ECNU
Copy link
Owner Author

cuteDen-ECNU commented Nov 26, 2023

bugtracker link: duckdb/duckdb-spatial#195
fix link: 56b17a1
reproduce: 27915ec

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

No branches or pull requests

1 participant