duckdb-web
duckdb-web copied to clipboard
duckdb
DuckDB website and documentation
Many pages, e.g. [`COPY`](https://duckdb.org/docs/archive/0.9/sql/statements/copy) have large SQL blocks with examples. I'd propose to break these up.
DuckDB supports queries like: SELECT .. FROM .. WHERE column > ALL|ANY|SOME (...subquery...) But it appears that this is not documented? Page URL:
The whole page is organized alphabetically, except for the temorary files section. Would make it easier to navigate if it was placed according to alphabetical order. Page URL:
This page is about keywords and identifiers, but also contains two sections about literals, https://duckdb.org/docs/sql/keywords_and_identifiers#string-literals and https://duckdb.org/docs/sql/keywords_and_identifiers#numeric-literals. I think these sections should not be here, whatever information they have should...
The information in the section "[Formatting Strings](https://duckdb.org/docs/sql/data_types/text#formatting-strings)" is really about string literals, which is described in detail in https://duckdb.org/docs/sql/data_types/literal_types#string-literals I suggest to remove the section and instead, include a single...
The https://duckdb.org/docs/sql/data_types/text page has a section about Double Quotes. This section is out of place as double quotes have nothing to do with the text type (or values of that...
On this page of the documentation: https://duckdb.org/docs/sql/statements/select#order-by-and-limit-clauses we see the syntax diagram for the ORDER BY and LIMIT clause  The diagram appears to imply that a LIMIT clause must...
See https://github.com/duckdb/duckdb/issues/12103
Add navigation buttons to the documentation as per the proposal here: https://github.com/duckdb/duckdb-web/issues/2852 Comments: 1. I was able to get this to work pretty well but there were a couple limitations....
See https://github.com/duckdb/duckdb/issues/12095