Stephan Georg

Yes, Bavaria even sued somebody (https://netzpolitik.org/2021/offene-geodaten-bayern-geht-gegen-open-data-aktivistinnen-vor/) for using the data. It's a mess and Bavaria (https://www.byte.bayern/) should shame for pretending being innovative in that regard.

What about SK,Slovensko,Slovensko,Slovakia ad- https://data.slovensko.sk/datasety/b27f57f1-7e76-45e0-8968-631f9176b2e9

Hi @lastarel Thank you for the PR. Could you please write a test for your scenario so I can review your changes?

Yes, the result parser is really static right now as you can see [here](https://github.com/StephanGeorg/node-dig-dns/blob/master/src/index.js#L13]) and has to be rewritten completely.

@sidroopdaska Have you found a solution/reason for the performance problem? I also have performance issues with my large table (118 million rows) which runs indefinitely even with simple queries. ```sql...

Yes, just did that. Thank you for mentioning this. For me it was not clear that ```sql SELECT * FROM large_table WHERE id = 1234; ``` is converted into ```sql...

Currently very confusing: **PostGIS** ```sql SELECT ST_GeomFromText('POINT(13 52)', 4326) -- SRID=4326;POINT(13 52) , ST_Transform(ST_GeomFromText('POINT(13 52)', 4326), 25833) -- SRID=25833;POINT(362705.634104228 5762926.812790221) ; ``` **DuckDB** ```sql SELECT ST_GeomFromText('POINT(13 52)') -- POINT (13...

Thanks @Maxxen. Great work by the way, sorry to not mention this before. 😬

Please provide some examples or test cases.

`"@duckdb/duckdb-wasm": "1.29.1-dev68.0"` & `INSTALL excel FROM core_nightly;` worked for me btw.