-
Notifications
You must be signed in to change notification settings - Fork 293
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
upsert broken in recent persistent versions #662
Comments
This should be fixed in this PR: #618 |
Update: It's not completely fixed and it seems to fail in some special case in recent version of postgresql 9.6. |
I have updated the PR to include the fixes. Can you give it a try and confirm if it works for you ? I have tested on Postgresql 9.5.4 and 9.6 and it works for me there. |
Yes, 22754d3 fixes the issue here! Thanks. -R |
|
A call to
upsert (Table 1 0) [TableCount +=. 1]
generates an SQL query likeNow PostgreSQL complains:
To fix this, column
"count"
should be qualified with the table. UsingSET "count"="table"."count"+1
works as expected.I tested this with PostgreSQL 9.6.2 and Persistent 2.6. Older versions of persistent where multiple queries were used did not have the problem.
The text was updated successfully, but these errors were encountered: