Re: Track changes to function code - Mailing list pgsql-general

From Jacob Bunk Nielsen
Subject Re: Track changes to function code
Date
Msg-id spamdrop+87d2cy99dm.fsf@atom.bunk.cc
Whole thread Raw
In response to Track changes to function code  (Rebecca Clarke <r.clarke83@gmail.com>)
Responses Re: Track changes to function code  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
Rebecca Clarke <r.clarke83@gmail.com> writes:

> At present when a function is being edited we keep note of when and
> by who within comments in the function's code.

That sounds cumbersome.

> Is there, or can anyone recommend, any open source software that
> tracks function activity when it comes to edits (not executions)? 

How about keeping the code outside of the database in a VCS such as git,
Subversion or whatever you are used to using for other code projects?

That will also make it possible easily go back to previous versions if
you should need to some day.

You simply put your functions in one or more .sql files that you
version control using e.g. git.

Once you have written your functions you can put them in you database
using:

psql -f myfile.sql

--
Jacob



pgsql-general by date:

Previous
From: Rebecca Clarke
Date:
Subject: Track changes to function code
Next
From: Pavel Stehule
Date:
Subject: Re: Track changes to function code