Update extension to DuckDBv1.1.0

[Dtenwolde]

What happens?

DuckDB released v1.1.0 https://github.com/duckdb/duckdb/releases/tag/v1.1.0

The extension should be updated

See #119 for instructions

We can also bump the community extension version once the transition is complete

To Reproduce

-

OS:

macOs 13 - Apple M1 Pro

DuckDB Version:

v1.1.0

DuckDB Client:

CLI

Full Name:

Daniel ten Wolde

Affiliation:

CWI

How did you load the extension?

Community extension version

Did you include all relevant data sets for reproducing the issue?

No - Other reason (please specify in the issue body)

Did you include all code required to reproduce the issue?

• [X] Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• [X] Yes, I have

[Dtenwolde]

Some minor changes:

• CTEs are now auto-materialized if they are referenced more than once. #133 introduced always materializing the shortest path CTE, but now this is automatically done, no longer explicitly.
• Minor differences in test results are due to the different ordering of tuples. I fixed this by adding ORDER BY to test cases making them deterministic.

[Dtenwolde]

The path-finding operator required a bit more changes. Still working on the optimizer rule to properly detect when to execute it

[Dtenwolde]

Submitted an update to the community extension repository to make DuckPGQ easily installable. https://github.com/duckdb/community-extensions/commit/56ea0de157bb9badb397d6eddd6c79df1650d3da

Closing this issue