| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Joel Jacobson <joel(at)trustly(dot)com>, Vik Reykja <vikreykja(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Schema version management |
| Date: | 2012-07-07 21:18:34 |
| Message-ID: | 15601.1341695914@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Aidan Van Dyk's message of sb jul 07 11:32:33 -0400 2012:
>> But, since you're using operators, what would you think is an
>> appropriate name for the file the operator is dumped into?
> I was thinking that it might make sense to group operators according to
> the type(s) they operate on, somehow. Using funny chars for names is
> guaranteed to cause problems somewhere.
Sure. You need not look further than "/" to find an operator name that
absolutely *will* cause trouble if it's dumped into a filename
literally.
I'm not especially thrilled by the idea of using url-encoding or
something like that for operator names, though. Seems like it loses on
readability.
If we think that operators outside of extensions will be an infrequent
special case, what about just dumping all of them into a single file
named "operators"? And similarly for casts?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2012-07-08 00:43:24 | Re: autocomplete - SELECT fx |
| Previous Message | Robert Haas | 2012-07-07 19:46:26 | Re: regex_fixed_prefix() is still a few bricks shy of a load |