Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to clarify the note on postgres support #32

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

jpcamara
Copy link
Contributor

  • On twitter, some folks (myself included) were confused about the note and thought it was implying some issue with using this gem with Postgres

  • This tries to emphasize first that all three are fully supported. Then it tries to specify a bit more clearly the distinction about the action cable built-in adapter vs solid cable

  • Also mentions potentially hitting issues with the payload size, or not wanting the NOTIFY command (which may be a problem for some folks using pgbouncer)

Copy link
Collaborator

@npezza93 npezza93 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise, looks good

README.md Outdated
> broadcasting large payloads, Solid Cable will work without a hitch.
> Solid Cable is tested to work with MySQL, SQLite, and PostgreSQL.
>
> Action Cable already has a [dedicated PostgreSQL adapter](https://github.com/rails/rails/blob/main/actioncable/lib/action_cable/subscription_adapter/postgresql.rb),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should point to the Rails docs here instead of the code. https://guides.rubyonrails.org/action_cable_overview.html#postgresql-adapter

* On twitter, some folks (myself included) were confused about the note and thought it was implying some issue with using this gem with Postgres

* This tries to emphasize first that all three are fully supported. Then it tries to specify a bit more clearly the distinction about the action cable built-in adapter vs solid cable

* Also mentions potentially hitting issues with the payload size, or not wanting the `NOTIFY` command (which may be a problem for some folks using pgbouncer)
@jpcamara jpcamara force-pushed the clarify-pg-support-docs branch from 1f49d9e to 8cf63af Compare September 19, 2024 14:12
@jpcamara
Copy link
Contributor Author

Good call @npezza93 - I just updated it to point at the rails docs instead

@npezza93 npezza93 merged commit ba1b1e5 into rails:main Sep 19, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants