Added PGSQL getListType function

Author: xvitcoder

autoload/dbext.vim

@@ -1996,9 +1996,9 @@ function! s:DB_ASA_stripHeaderFooter(result)
     " table_name         table_id
     " ---------------------------
     " ZTSAAP_C_OPKEY     867
-    " 
+    "
     " (1 rows)
-    " 
+    "
     " Execution time: 0.025 seconds
 
     " Strip off column headers ending with a newline
@@ -3782,6 +3782,19 @@ function! s:DB_PGSQL_getListProcedure(proc_prefix)
     return s:DB_PGSQL_execSql(query)
 endfunction
 
+function! s:DB_PGSQL_getListType(type_prefix)
+    let owner   = s:DB_getObjectOwner(a:type_prefix)
+    let object  = s:DB_getObjectName(a:type_prefix)
+    let query = "  SELECT t.typname AS type, e.enumlabel AS value, pg_get_userbyid(u.usesysid) AS owner " .
+                \ "  FROM pg_user u, pg_type t JOIN pg_enum e ON e.enumtypid = t.oid " .
+                \ " WHERE t.typowner = u.usesysid " .
+                \ "   AND u.usename  like '" . owner . "%' " .
+                \ "   AND p.proname  like '" . object . "%' " .
+                \ " ORDER BY t.typname"
+
+    return s:DB_PGSQL_execSql(query)
+endfunction
+
 function! s:DB_PGSQL_getListView(view_prefix)
     let owner      = s:DB_getObjectOwner(a:view_prefix)
     let view_name  = s:DB_getObjectName(a:view_prefix)
@@ -6295,6 +6308,23 @@ function! dbext#DB_getListProcedure(...)
     return dbext#DB_execFuncTypeWCheck('getListProcedure', proc_prefix)
 endfunction
 
+function! dbext#DB_getListType(...)
+    if(a:0 > 0)
+        " Strip any leading or trailing spaces
+        let type_prefix = substitute(a:1,'\s*\(\w*\)\s*','\1','')
+    else
+        let type_prefix = s:DB_getInput(
+                    \ "Enter type prefix: ",
+                    \ '',
+                    \ "dbext_cancel"
+                    \ )
+        if type_prefix == "dbext_cancel"
+            return ""
+        endif
+    endif
+    return dbext#DB_execFuncTypeWCheck('getListType', type_prefix)
+endfunction
+
 function! dbext#DB_getListView(...)
     if(a:0 > 0)
         " Strip any leading or trailing spaces

doc/dbext.txt

@@ -125,14 +125,14 @@ Version 23.00 (Dec 30, 2015)
  - 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 
+ - 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 
+ - 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) 
+ - For PGSQL, use the "schemaname" column rather than "tableowner" (pull #15)
    (Stefan Litsche)
 
 
@@ -162,12 +162,12 @@ Version 22.00 (August 2, 2015)
    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.  
+   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 
+   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
@@ -1197,7 +1197,7 @@ Version 2.00 (Jul 11, 2004)
               let dbext_default_query_statements = 'select,update';
     dbext_default_passwd_use_secret
 <       - 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 
+          a GUI version of Vim, the prompt is not displayed in a dialog unlike
           the other parameters.  This option is OFF (0) by default. >
     dbext_default_parse_statements
 <       - Which statements are parsed for input parameters (See |dbext-newdb|) >
@@ -1337,7 +1337,7 @@ Version 2.00 (Jul 11, 2004)
           the statement to a String.
 >
     dbext_default_strip_at_variables
-<       - A buffer local variable which is used when executing SELECT 
+<       - A buffer local variable which is used when executing SELECT
           statements.  This setting is OFF by default and ON for SQLSRV and
           ASE databases.  Most databases support the INTO clause which is used
           to store column values into locally declared
@@ -1350,19 +1350,19 @@ Version 2.00 (Jul 11, 2004)
             BEGIN
                 DECLARE @fname VARCHAR(30);
                 DECLARE @lname VARCHAR(30);
-                
+
                 -- TransactSQL syntax
                 SELECT @fname = FirstName, @lname = Surname
                   FROM Customer
                  WHERE ID = @p1
             END;
 <
         - If you visually selected the SELECT statement in this procedure
-          to test it, you will get a syntax error indicating "@fname" is 
+          to test it, you will get a syntax error indicating "@fname" is
           not defined.  When the procedure executes, the variable is defined
           and will execute correctly.
         - The "strip_at_variables" is enabled for all SQLSRV and ASE databases
-          which use TransactSQL syntax.  When strip_at_variables = 1, 
+          which use TransactSQL syntax.  When strip_at_variables = 1,
           and visually selecting the statement and executing, the variable
           assignments are stripped so that the developer can see the result set
           returned by the query (instead of a syntax error): >
@@ -1379,7 +1379,7 @@ Version 2.00 (Jul 11, 2004)
             let g:dbext_default_profile_SQLSRV = 'type=SQLSRV:user=sa:passwd=Leader:strip_at_variables=0'
 >
     dbext_default_strip_into
-<       - A buffer local variable which is used when executing SELECT 
+<       - A buffer local variable which is used when executing SELECT
           statements.  This setting is ON by default and OFF for SQLSRV and
           ASE databases.  Most databases support the INTO
           clause which is used to store column values into locally declared
@@ -1388,32 +1388,32 @@ Version 2.00 (Jul 11, 2004)
             BEGIN
                 DECLARE @fname VARCHAR(30);
                 DECLARE @lname VARCHAR(30);
-                
+
                 SELECT FirstName, Surname
                   INTO @fname, @lname
                   FROM Customer
                  WHERE ID = @p1
             END;
 <
         - If you visually selected the SELECT statement in this procedure
-          to test it, you will get a syntax error indicating "@fname" is 
+          to test it, you will get a syntax error indicating "@fname" is
           not defined.  When the procedure executes, the variable is defined
           and will execute correctly.
         - The "strip_into" is enabled for all databases other than SQLSRV
-          and ASE which use TransactSQL syntax.  When strip_into = 1, 
+          and ASE which use TransactSQL syntax.  When strip_into = 1,
           and visually selecting the statement and executing, the INTO
           clause is stripped so that the developer can see the result set
           returned by the query (instead of a syntax error): >
                 SELECT FirstName, Surname
                   FROM Customer
                  WHERE ID = @p1
 <
-        - For SQLSRV databases, the INTO clause is used to create a 
+        - For SQLSRV databases, the INTO clause is used to create a
           temporary table and return the results from it.  So for this
           database, we do not want to strip the INTO clause.  Consider
           this SQL statement: >
-            SELECT * 
-              INTO dbo.Table_backup 
+            SELECT *
+              INTO dbo.Table_backup
               FROM dbo.Table;
 <
         - It may be necessary to toggle this setting on and off based
@@ -2438,6 +2438,7 @@ Version 2.00 (Jul 11, 2004)
     DB_NEW_getDictionaryView
     DB_NEW_getListColumn
     DB_NEW_getListProcedure
+    DB_NEW_getListType
     DB_NEW_getListTable
     DB_NEW_getListView
     DB_NEW_stripHeaderFooter