Re: Schema version management

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:20:28
Message-ID: 1342041031-sup-4511@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Peter Eisentraut's message of mié jul 11 17:03:03 -0400 2012:
>
> 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).

operator_!___numeric.sql (postfix, name does not need escape)
operator_%7C%2F_integer__.sql (prefix)
operator_%3C_bit_varying__bit_varying.sql (type name with spaces,
changed to _)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Thornton 2012-07-11 21:32:33 Re: DELETE vs TRUNCATE explanation
Previous Message Andrew Dunstan 2012-07-11 21:04:39 Re: DELETE vs TRUNCATE explanation