Hi 2014-07-21 14:36 GMT+02:00 Jacob Bunk Nielsen <ja...@bunk.cc>:
> Rebecca Clarke <r.clark...@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 > yes, it is good way stored procedures are code as any other and there are same rules. Use files, use a your preferred editor, use makefiles, use GIT Regards Pavel Stehule > > -- > Jacob > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
