We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've figured out the bug which was preventing the statement cache being used with array associations.
Unfortunately, I'm unlikely to get around to opening a PR for it in the near future.
My fork is very different (I've stripped out parts of the library I'm not using, to reduce the chance of conflicts with core rails), but cb76495 over on https://github.com/radiopaedia/torque-postgresql/tree/just_has_one should point you in the right direction.
The text was updated successfully, but these errors were encountered:
Looks like there's still an issue where it'll sometimes create too many bind params, actually - possibly not as useful as I'd hoped.
Sorry, something went wrong.
No branches or pull requests
I've figured out the bug which was preventing the statement cache being used with array associations.
Unfortunately, I'm unlikely to get around to opening a PR for it in the near future.
My fork is very different (I've stripped out parts of the library I'm not using, to reduce the chance of conflicts with core rails), but cb76495 over on https://github.com/radiopaedia/torque-postgresql/tree/just_has_one should point you in the right direction.
The text was updated successfully, but these errors were encountered: