| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: function parse_ident |
| Date: | 2015-08-19 23:20:40 |
| Message-ID: | 55D50F48.7000501@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/19/15 2:44 PM, Pavel Stehule wrote:
> Don't say "parse names for things other than tables". Only a minority
> of the types of objects used in the database have names that meet this
> specification.
Really? My impression is that almost everything that's not a shared
object allows for a schema...
> I see one important reason and one minor reason:
>
> Important - cast to regclass is possible only for existing objects -
> parse_ident doesn't check validity of parsed ident.
> minor - cast to regclass depends on search_path - but parse_ident not -
> with this function I am able to detect if ident depends (or not) on
> search_path.
I've been forced to write this several times. I'd really like to expose
this functionality.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-08-20 00:05:48 | Re: Badly broken logic in plpython composite-type handling |
| Previous Message | Jim Nasby | 2015-08-19 23:16:38 | Re: Freeze avoidance of very large table. |