drizzle-orm-docs

Addresses drizzle-team/drizzle-orm#6101. The page renders every entry under , and the two newest are (2025-02-12) and / (2024-08-05). Since nothing has been added since, the page reads as if the last release was over a year ago, while the actual latest release on GitHub is much more recent. As the reporter put it, it makes the project look abandoned. This adds one line under the heading explaining that the page only covers releases with written-up notes, and linking to the GitHub releases for the full list: This page only covers releases we've written up in detail, so it's not a complete or up to date list. For every release, see the releases on GitHub. The alternative the issue also mentions is backfilling the page with every release since 0.32.2, or dropping it entirely and redirecting to GitHub. Both are calls for the team to make, so I went with the smallest change that stops the page from misleading people. Happy to switch to either if you'd prefer. Styling follows the existing conventions in the component (scoped styles, override, mobile size in the existing media query), and for the external link to match the rest of the repo. Verification: , (0 errors, 0 warnings, 11 pre-existing hints), (29 passed), and checked the rendered page on .

The many-to-many relations documentation recommends creating a separate composite index on in addition to a composite primary key on . In PostgreSQL (and most other DBMSs), the PK already creates a unique index covering , making the additional composite index redundant. So this: Should be:

1. Incorrect example output in relation section At the beginning of the section, the example output contradicts the relation definition. The relation is defined as , meaning should match . However, the example output shows: and are inconsistent. One of them should be corrected (e.g., should be ). 2. Incorrect field in section In the section, the relation incorrectly uses the same foreign key as the relation. Current code: Since is defined with , the relation must use a different foreign key column (e.g., ). Currently, this snippet would cause an "not enough information to infer relation" error.