-
Notifications
You must be signed in to change notification settings - Fork 52
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
PG::InvalidTextRepresentation #34
Comments
Same here. |
Same here. It seems this is introduced in commit c9b7928. Any ideas why these single quotes were introduced here? |
Same here. Any working fixes? |
I'm having the same problem. Any ideas? |
Same here, pleaeaease fix. |
Same problem here. Downgrade to 0.0.9 makes it work. |
* leonardvandriel/master: Fix incorrect extraneous quoting (issues tlconnor#34 and tlconnor#37)
Had the same problem, downgraded to 0.0.9 |
Hi everyone. As you've probably noticed I am no longer maintaining this project. The main reasons being that I no longer have the luxury of working with PosgreSQL. If someone here would be willing to take over maintenance I could give them write access, or alternatively I could create a new github account and transfer the repo over. |
Hi Tim, thanks for the work so far. I have to pass your offer, since I'm upgraded to Rails 4 recently and removed the gem. |
The same here, downgraded to 0.0.9 and everything working again. Thanks @tlconnor for the hard work. |
My 2c: Rails 4 has native support for array, hstore and json. Upgrading is really worth it. 😃 ~Marcello~ [email protected]
|
Upgrading to v0.0.10 breaks my current application.
PG::InvalidTextRepresentation: ERROR: array value must start with "{" or dimension information
I receive this error if the array is empty, haven't tested with an array with values.
Version v0.0.9, which doesn't throw error
Version v0.0.10, which throws error
I'm on Postgres 9.1.3.
The text was updated successfully, but these errors were encountered: