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

Fix search on Oban.Pro #11

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Fix search on Oban.Pro #11

merged 1 commit into from
Nov 25, 2024

Conversation

maltoe
Copy link
Contributor

@maltoe maltoe commented Nov 25, 2024

Hi @egze ,

me again. Patch from this morning fixed it for our app in :dev where we use the Basic engine, but not in :prod where we have Oban.Pro. 🤦

The adapter detection we implemented in 30e2d6c doesn't work for Oban.Pro when one uses the Smart engine. Changed to a) assume Postgres for both Basic and Smart, b) let the fallback also explicitly type cast the jsonb column, which I believe shouldn't matter on sqlite.

The adapter detection we implemented in 30e2d6c doesn't work for Oban.Pro
when one uses the `Smart` engine. Changed to a) assume Postgres for both
`Basic` and `Smart`, b) let the fallback also explicitly type cast the jsonb
column, which I believe shouldn't matter on sqlite.
@egze egze merged commit b562396 into egze:main Nov 25, 2024
1 check passed
@egze
Copy link
Owner

egze commented Nov 25, 2024

Thanks. Just curious, why don't you use also Pro in development?

@maltoe maltoe deleted the fix-search-on-oban-pro branch November 25, 2024 21:23
@maltoe
Copy link
Contributor Author

maltoe commented Nov 25, 2024

Nevermind, I double checked and we are using Pro in development. Must have tried it before doing the engine conditional.

Thanks for being so quick with the releases.

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.

3 participants