-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Failure on postgres when table name is domains #1028
Comments
Thank you for reporting this issue.
Yes, please report the postgres version you are running. Please also report other relevant versions (OS, PHP, etc). NB: Did you run the tests? |
Sorry, not my best bug report ever :)
This always returns data, even if you don't have a domains table (but when you do have that table this becomes an issue). It did just ran the tests, they complete fine, but there is no domains table there :) |
This domains thing is something new in PostgreSQL? Do you know what the |
Can you test the latest master? |
Somehow the namespaces outside public where also evaluated. I restricted all reflection to the 'public' namespace, while I can imagine that people have other namespaces than public, so maybe it needs to be configurable. |
This shows the namespaces:
And the namespace that causes the problem:
Maybe the excluding condition should be:
What do you think? |
Can you test the latest master? |
Yes, latest master works, nice! |
Released in v2.14.26 |
@tjikkun Dankjewel voor je bijdrage / Thank you for your contribution! |
When creating a table in postgres with:
I get the following error
It seems it pulls in column names that are internal to postgres domains.
The text was updated successfully, but these errors were encountered: