| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joel Jacobson <joel(at)trustly(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Schema version management |
| Date: | 2012-07-12 14:17:46 |
| Message-ID: | 4FFEDC8A.4010200@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/12/2012 10:01 AM, Tom Lane wrote:
>
> FWIW, I think you could save a level of naming if you were willing to
> put the type first, since the type would imply whether the object
> lives in a schema or not:
>
> [type]/[name].sql
> [type]/[schema]/[name].sql
>
>
That will destroy the property of having everything for a given schema
collected together.
Arguably we should make a special case for the create statement of a
schema, but I'm not even sure about that.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-07-12 16:07:13 | Re: several problems in pg_receivexlog |
| Previous Message | Joel Jacobson | 2012-07-12 14:14:17 | Re: Schema version management |