Re: New Procedurs With Version# In Name

From: Shakespeare <whatsin_at_xs4all.nl>
Date: Fri, 12 Mar 2010 10:12:53 +0100
Message-ID: <4b9a05ab$0$22917$e4fe514c_at_news.xs4all.nl>

Op 11-3-2010 6:17, Mladen Gogala schreef:
> On Wed, 10 Mar 2010 21:07:50 -0800, jeffchirco_at_gmail.com wrote:
>
>> So when my developers need to make a change to a procedure, instead of
>> just recompiling the procedure they want to create a new procedure named
>> like sp_procedure2 and then use the new procedure in their application.
>
> Have your developers ever heard of something called "versioning system"?
> There are several of those which are widely used. The names you will most
> frequently encounter are git, svn and CVS. Those things can really help
> with versions, branches and revisions. There are also commercial products
> which do the same thing, but with a better GUI. Personally, I think that
> GUI is for wimps, especially when it comes to versioning systems. One
> should learn the CVS syntax by heart and know how to diff, how to see the
> revision log, check in a new version, merge 2 branches etc.
>
>
>

And I thought SourceSafe was a versioning system.... Versioning systems won't help if both versions of the procedure must be kept in the software, indeed because other programs may need the old version when they can not handle changes made to the original procedure. I agree that versioning within the code is not the best way, but sometimes it can not be avoided. But the new procedure should not be considered a new version, but a complete new procedure, and like Álvaro states, be given a new name. If both procedures share a lot of code, the duplicate part should be taken out and be programmed as a separate procedure and be called by both procedures.

Shakespeare Received on Fri Mar 12 2010 - 03:12:53 CST