README: link ArcadeDB's own account of the integration - #149
Merged
Merged
Conversation
ArcadeDB published "ArcadeDB in the Apache Arrow Ecosystem, Through Its PostgreSQL Wire Protocol" on 2026-09-21. It was linked from COMPATIBILITY.md, the ArcadeDB database page and the landing card, but not from the README, which is where most people arrive. States what the tracker states: all four gaps are fixed, one by a pull request from here (#7815), and #8090 within a day of being filed. Recounted from docs/UPSTREAM.md rather than from the earlier draft of this paragraph, which read as though only three were fixed. The link is the plain post URL; the campaign's utm parameters are theirs and do not belong in a permanent reference.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ArcadeDB published ArcadeDB in the Apache Arrow Ecosystem, Through Its PostgreSQL Wire Protocol on 2026-09-21 — their own account of the integration and of the four protocol gaps this driver found in their PostgreSQL wire.
It was already linked from
docs/COMPATIBILITY.md, the ArcadeDB database page and the landing card, but not from the README, which is where most people actually arrive. This adds it beside the omniload paragraph, since both are third parties engaging with the project rather than claims we make about ourselves.Two deliberate choices:
docs/UPSTREAM.mdhas five ArcadeDB rows, four of which are defects and all four say fixed — the fifth is the native-probe discussion. The paragraph now says all four are fixed, names #7815 as the one that came from here, and notes #8090 was fixed within a day of being filed and verified on the 26.10.1 snapshot.utm_source=linkedin&utm_campaign=arrow-adbcparameters. Those belong to their campaign; a permanent reference in our README should not carry someone else's tracking.Verified the post is still live (HTTP 200) and that it names adbcBridge 33 times with 8 links to adbcbridge.org, so the description is accurate.