mirror of
https://github.com/postgres/postgres.git
synced 2025-06-29 10:41:53 +03:00
Allow psql's \df and \do commands to specify argument types.
When dealing with overloaded function or operator names, having to look through a long list of matches is tedious. Let's extend these commands to allow specification of (input) argument types to let such results be trimmed down. Each additional argument is treated the same as the pattern argument of \dT and matched against the appropriate argument's type name. While at it, fix \dT (and these new options) to recognize the usual notation of "foo[]" for "the array type over foo", and to handle the special abbreviations allowed by the backend grammar, such as "int" for "integer". Greg Sabino Mullane, revised rather significantly by me Discussion: https://postgr.es/m/CAKAnmmLF9Hhu02N+s7uAyLc5J1xZReg72HQUoiKhNiJV3_jACQ@mail.gmail.com
This commit is contained in:
@ -1062,10 +1062,16 @@ patternToSQLRegex(int encoding, PQExpBuffer dbnamebuf, PQExpBuffer schemabuf,
|
||||
* regexp errors. Outside quotes, however, let them pass through
|
||||
* as-is; this lets knowledgeable users build regexp expressions
|
||||
* that are more powerful than shell-style patterns.
|
||||
*
|
||||
* As an exception to that, though, always quote "[]", as that's
|
||||
* much more likely to be an attempt to write an array type name
|
||||
* than it is to be the start of a regexp bracket expression.
|
||||
*/
|
||||
if ((inquotes || force_escape) &&
|
||||
strchr("|*+?()[]{}.^$\\", ch))
|
||||
appendPQExpBufferChar(curbuf, '\\');
|
||||
else if (ch == '[' && cp[1] == ']')
|
||||
appendPQExpBufferChar(curbuf, '\\');
|
||||
i = PQmblen(cp, encoding);
|
||||
while (i-- && *cp)
|
||||
{
|
||||
|
Reference in New Issue
Block a user