-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Doctrine\DBAL\Exception\InvalidFieldNameException when working with DB schema on PostgreSQL 10 #2868
Comments
Suggested solution:
to :
|
PostgreSQL 10 is out of beta now: https://www.postgresql.org/about/news/1786/ |
First we will need Travis CI to support it: travis-ci/travis-ci#8537 |
when it is going to be migrated? it definently solves the problem, and because of new sequence architecture on postgresql 10 we can't define a generic method for that. |
Just tried @wzator's changes and it works fine here 👍 |
have this problem in doctrine2 using in symfony 3.3 version. no matter which ,,auto-identity'' aproach I chose, I got this error too. change suggested by wzator few lines above this solved the problem temporarily. thx for that. |
We are waiting for PSQL10 support in Travis I guess. Meanwhile you can use code from my PR. #2893 |
thank you, i'll analyze your commit and use it. |
Guys, what the status of the issue?? When we can expect fix? |
Read the comments please |
#2893 has been merged and added Postgres 10 support, closing this one as duplicate. |
@wzator´s suggestion worked perfectly!!! |
@wzator's suggestion worked like a charm. You can find this file in
|
Hey, The erroneous $data assignment is now in line 311 and fetchAssoc() is used instead of fetchAll(). For me, the following adjustment worked:
with:
|
First a failing test case |
I confirm that the problem still occurs with PostgreSQL 10.5 and doctrine/dbal 2.8.0. |
DBAL is working as expected with PostgreSQL 10+, this is very likely a configuration issue in your code where you are not specifying serverVersion correctly. The code path in question is covered by tests and tested against all PostgreSQL 9.x, PostgeSQL 10 and PostgreSQL 11 (this condition is not entered with PostgreSQL 10+ since these metadata are provided by the platform ahead). Anyway, if you still feel this is a Doctrine issue rather than a configuration issue, please open new issue with failing test. |
Since upgrading to PostgreSQL 10 I have an error in my projects using Doctrine when I trying to generate migrations or just check the schema difference:
Seems like it's related to nextcloud/server#5930 where @justin-sleep wrote:
The text was updated successfully, but these errors were encountered: