I'm putting these issues that I found here, so we can better keep track of them.:
[ ] Code snippets have confusing color fonts. Some keywords are black and others are red.
[ ] The larger purpose of the DuckDB -> One important use case of the DuckDB Scanner extension is ...
[ ] MATCH (p:person) RETURN p.*; -> p:Person. (In addition the result table's schema is wrong: "s.name | s.age").
[ ] PostgreSQL databases that are persisted to disk -> remove the part about "persisted to disk".
[ ] Clarify that the extension is only to scan data and not to write any data.
[ ] Official extensions can be simply installed by running the install command:-> Say that this can be executed from the CLI or any programming language.
[ ] Prerequisites before using DuckDB extension? Are there any (e.g., brew install DuckDB) or no. For DuckDB, it has to be 0.10.x.
[ ] Document about DuckDB and Postgres schema cache
[ ] Document that each time you create a new Database cpp object, which happens when you start your CLI again, or start your python script or cpp code again, you need to LOAD each EXTENSION. => Main extensions page.
[ ] Document that Postgres extension should work with any relatively recent Postgres version (e.g., 14 and above and possibly earlier versions).
[ ] Test that if you don't have DuckDB, you can still use the Postgres extension. Test this after Chang handles the static linking to DuckDB.
I'm putting these issues that I found here, so we can better keep track of them.: