-
Notifications
You must be signed in to change notification settings - Fork 48
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
Issue with PostgreSQL adapter: ActiveRecord::StatementInvalid: PG::ProtocolViolation: ERROR #14
Comments
Hi, @bbonamin. Thank you for reporting this! @derencius is working on it though. |
This is great! Thanks. I didn't even think of checking the open pull requests 😖 ! |
Same issue here, I'll also follow that PR :) |
Here's the PR, folks! I'd love for y'all to provide some feedback. |
solved! |
Thanks @nettofarah and @derencius 💯 👍 💯 ! |
@bbonamin, @derencius, @jlerpscher mind helping us with the survey on #19? |
Hello!
Thank you for open sourcing this gem, think it's a brilliant idea. I've been able to give it a try with sqlite3, but I haven't had much luck making it work with PostgreSQL. (Latest Rails 4.2 and Ruby 2.2.3)
Given a User model, with a attribute of
name
, if one is present in the database; when I runPolo.explore(User, 1)
, I get the following stack trace:Here's a sample application that exhibits this behavior: https://github.com/bbonamin/polo_rails_test
Let me know if I can be of any help :) To be honest I'm kind of lost on where to go an fix this, but apparently it's related to the fact that PostgreSQL validates prepared statements. rails/rails#20077
The text was updated successfully, but these errors were encountered: