Re: schema change tracking
От | Adrian Klaver |
---|---|
Тема | Re: schema change tracking |
Дата | |
Msg-id | 7d976b63-674f-5901-6f02-e9571751e502@aklaver.com обсуждение исходный текст |
Ответ на | Re: schema change tracking (Benedict Holland <benedict.m.holland@gmail.com>) |
Список | pgsql-general |
On 5/16/19 10:55 AM, Benedict Holland wrote: > Hi All! > > Thanks for the replies. I am looking for a solution, possibly 3rd party, > where I write changes to the schema and it keeps track of the changes I > made. I am used to doing stuff in pgadmin4 but I don't mind something else. > > This isn't really ad-hoc. This is more like, I have a v1.0 release > coming out soon and I have made dozens or hundreds of changes to the > schema from the alpha. Right now, I can destroy the databases and > recreate them without data loss because it is in active development. > When this gets released, we need some way to make sure that we can > easily migrate between release versions and that means schema change > tracking. Basically, to Steve's concern, I don't have to go back and > figure out changes (thankfully, I have done that and it sucks) but we > need something from an initial release moving forward. > > I don't have time to write my own and this problem is complex enough to > either buy a solution or go with a 3rd party application. > > So far, SQITCH is looking like a winner. Yoyo can work as I have access > to python. We are not using SQLAlchemy but I don't see a reason why we > can't. I will second the motion on Sqitch. It has met all my needs and is framework agnostic. > > Thanks all for the suggestions. This is great. > ~Ben > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: