| From: | Greg Williamson <gwilliamson39(at)yahoo(dot)com> |
|---|---|
| To: | akp geek <akpgeek(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: version controlling postgresql code |
| Date: | 2012-02-28 20:36:40 |
| Message-ID: | 1330461400.51883.YahooMailNeo@web46104.mail.sp1.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
akp geek asked:
>
> Would like to know if any one of you have used CVS or some other version controlling tools to version the postgres code? Any recommendations? Appreciate your help
>
>
I used CVS at previous jobs.
Currently the place I work uses git and a set of rules for programmers who create DDL changes, including rollback options (such as renaming columns to dropme_xxx instead of simply dropping them outright in the first change set).
The SQL files are checked in with a timestamp which controls the order of updates when we apply them to runtime.
I've had unpleasant experiences with commercial tools; CVS works well for simple environments and git can be used for more tangled development work.
HTH,
Greg Williamson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clodoaldo Neto | 2012-02-28 20:39:12 | Error installing plpythonu in 9.1 |
| Previous Message | hamann.w | 2012-02-28 20:36:23 | Re: what Linux to run |