We create a text file for each stored procedure and trigger (with the
"alter" command at the top of the file) and modify these files and run
them against the databases during development and testing. We version
control those text files. It is very rare for us to modify a stored
procedure or trigger directly in a production database, we create build
scripts from all of our changes and run those against production to
bring them up to date.

-steve

bill_lam wrote:

> I use subversion for version control for source code. If I rewrite some data
> logic using firebird's sp, then how to use subversion (or other cvs) to control
> these sp source code?
>
>