Skip to content
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

Postgres search_path relies on schema rather than tableowner. #15

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

slitsche
Copy link

@slitsche slitsche commented Oct 2, 2015

For PostgreSQL:
Change the table description and table complete list from tableowner to schemaname because the object resolution in Postgres relies on schema in search_path. See http://www.postgresql.org/docs/9.4/static/ddl-schemas.html

@dfishburn
Copy link

The schemaname v tableowner has been incorporated into dbext 23.00.
The duplicate helptag has been fixed as well.

@dfishburn
Copy link

Since you use PGSQL, can you have a look at pull #9 and see if you can correct the join so I can update dbext.

vim-scripts pushed a commit that referenced this pull request Jan 4, 2016
Posted by David Fishburn

New Features
------------
- Added a new database, CrateIO (Mathias Fussenegger)
- CRATE native database type and Crate via DBI are supported
- Updated the DBI SQLAnywhere procedure list to respect the option of whether to include the object owner names
- Added a new public function, DB_DictionaryDelete, to be used by the OMNI SQL Completion plugin (autoload/sqlcomplete.vim, which is part of Vim)

Bug Fixes
---------
- helptags reported duplicate tag MyProjectDir, updated documentation as a work around as there is no way to escape the real syntax (pull #3) (mexpolk)
- For PGSQL, use the "schemaname" column rather than "tableowner" (pull #15) (Stefan Litsche)
…cribeProcedure. Also adjusted DBListColumn to use schema name instead of owner.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants