-
Notifications
You must be signed in to change notification settings - Fork 158
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
Fix issue #611 #642
Fix issue #611 #642
Conversation
``` STATEMENT: SELECT table_name, column_name, pg_get_serial_sequence (table_name, column_name) FROM information_schema.columns WHERE table_schema = 'public' AND pg_get_serial_sequence (table_name, column_name) IS NOT NULL; ERROR: relation "information_schema_catalog_name" does not exist ```
I don't see why the Wouldn't it be safer to only select table_name and column_name (filtered by table_schema) in the For example:
or maybe
|
I presume that WITH clauses are always evaluated before the selected columns, but I did expect a solution like Timo's first example (because it's clearer that the pg_get_serial_sequence is done later). Don't mind either way, but would like to see a summary of the explanation from #611 in a comment above the statement. |
Co-Authored-By: Matt Mundell <32057441+mattmundell@users.noreply.github.com>
Thank you! |
Will you merge this into gvmd-8.0 as well? |
PR for this: #691 |
This PR fixes bug described here #611