Fixing join in DBListColumns #9
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without using the `oid` field to join we can get an error: "dbext:Table not found" when the relfilenode is not equal the relation's oid.
|
Thanks for the update, change will be part of dbext 22.0 Can you figure out what is wrong with this query and how to fix it. It is from the function s:DB_PGSQL_describeProcedure(procedure_name): It returns the following error: Thanks, |
vim-scripts
pushed a commit
that referenced
this pull request
Aug 12, 2015
Posted by David Fishburn New Features ------------ - Overhauled the prompting for SQL statement variable substitution (i.e. host variables, named parameters, question marks, ...). The actions and user interface are hopefully more clear, useful and efficient. For a full updated tutorial on how it works see :h dbext-tutorial-variables - Saved variables can now hold multiple values for the same parameter, see :h dbext-tutorial-variables for how it works. - Added C++ language support for variables (pull #12) (Anatolii Sakhnik). - Added the ability to specify special characters (i.e. "\t") for column delimiters when using ODBC or DBI database types (Michael Krnac). - Added new option, "passwd_use_secret", which is used when entering a password, if the value should be masked. When using a GUI version of Vim, the prompt is not displayed in a dialog unlike the other parameters. This option is OFF (0) by default. (pull #13) (petteja) - Added new option, "strip_into", which is used when executing statements which have variable assignments using the INTO clause. To test these queries, you need to remove the INTO clause so that when they execute the query you can see the result set returned. This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the INTO clause may be the wrong action. Now it can be controlled using this setting. This can also be set / overridden using DBSetOption strip_into=1 or as part of a dbext profile. - Added new option, "strip_at_variables", which is executing statements which have variable assignments in the SELECT list instead of the INTO clause. To test these queries, you need to remove the assignments when they execute to see the result set returned. This was on for all databases, but for TransactSQL or TSQL databases like SQLSRV and ASE, stripping the variable assignments in the SELECT list is required. This can be controlled via this setting. This can also be set / overridden using DBSetOption strip_at_variables=1 or as part of a dbext profile. Bug Fixes --------- - Minor correction to DBSetVar example (Cedric Simon). - When deleting a buffer, all syntax highlighting of your existing buffer is sometimes lost, which was a problem with one of the dbext autocmds (Anatolii Sakhnik). - Update Postgres get column list join conditions (pull #9) (Dickson S. Guedes). - dbext autocmd for checking for modelines messed up the jumplist (Justin M. Keyes)
|
Released with dbext 23.00 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without using the
oidfield to join we can get an error: "dbext:Table not found" when the relfilenode is not equal the relation's oid.