| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, 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>, 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-11 21:03:03 |
| Message-ID: | 1342040583.2712.13.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2012-07-10 at 17:54 -0400, Andrew Dunstan wrote:
> In general, NTFS forbids the use of these printable ASCII chars in
> filenames (see
> <http://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations>:
>
> " * : < > ? \ / |
> Many of these could be used in operators.
Yeah, that's a bummer. Then I guess some escape mechanism would be OK.
I could imagine an operator < on a custom data type being dumped into a
file named operator_%3C.sql. Still better than putting them all in one
file.
Of course, argument types need to be dealt with as well, just like with
functions (plus prefix/postfix).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-11 21:03:35 | Re: [PATCH] lock_timeout and common SIGALRM framework |
| Previous Message | Tom Lane | 2012-07-11 20:59:11 | Re: [PATCH] lock_timeout and common SIGALRM framework |