| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Mark Lubratt <mark(dot)lubratt(at)indeq(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] Schema comparisons |
| Date: | 2004-02-29 02:01:35 |
| Message-ID: | 11549.1078020095@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Richard Huxton <dev(at)archonet(dot)com> writes:
> I've been looking at storing $REVISION$ in comments for each object, so my
> install scripts can halt if there is a problem. Not wanting to use my only
> comment slot for this I was thinking about an extension to the COMMENT ON
> statement:
> COMMENT ON TABLE foo IS 'This is where I stroe my foos.';
> COMMENT ON TABLE foo SECTION 'default' IS 'I meant store my foos.';
> COMMENT ON TABLE foo SECTION 'revision' IS '1.19';
> COMMENT ON TABLE foo SECTION 'bar' IS 'baz';
This seems a little, um, specialized. Why don't you just keep the info
in a user-defined table?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex J. Avriette | 2004-02-29 02:23:48 | Re: [ADMIN] Schema comparisons |
| Previous Message | cmeinhardt | 2004-02-29 01:48:36 | unsubscribe |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex J. Avriette | 2004-02-29 02:23:48 | Re: [ADMIN] Schema comparisons |
| Previous Message | Kaare Rasmussen | 2004-02-29 01:35:59 | Re: Collaboration Tool Proposal |