?

Log in

During DB development it became clear, that using a version control system (VCS) for sources ... - PostgreSQL [entries|archive|friends|userinfo]
PostgreSQL Users

[ website | PostgreSQL Web site ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

During DB development it became clear, that using a version control system (VCS) for sources ... [Jan. 12th, 2008|08:07 pm]
PostgreSQL Users

postgresql

[poige]
... in PlPgSQL (and might be for table definitions as well) is rather highly preferable. However, I haven't found a suitable tool yet. It seems that the simpliest way is to dump a DB with Postgresql's pg_dump and then put the source under VCS, but this is poorly satisfactory. I deem the better solution would be a tool ``decomposing'' this dump into a chunk-files, containing only one function definition perhaps with other needed entities. Yeah, this is not too hard to write by myself, but if there's something better (or at least already written) available, I'd use it. :-)
linkReply

Comments:
[User Picture]From: xyphoid
2008-01-13 12:46 am (UTC)

Re: > to write all the schemas ourselves in an editor

Yeah, it required us to get out of the habit of working on the database directly. However, this actually helped a lot, as mentioned - it's really easy to end up with a messy database if you have several people working on one copy, and don't track changes.

Doesn't help much with dealing with changes to a live database, though.

pg_dump was still pretty useful, when you're (for example) adding indexes while optimising, you can just pg_dump after you're happy and grab the CREATE INDEX statements to add to your DDL.
(Reply) (Parent) (Thread)