Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control: History/Log

Categories

JUMP TO ANOTHER FORUM

(thinking…)

object revisions

Perhaps this already exists, but I couldn't easily find it by searching. We are using SVN as a backend. When checking in files, the "revision" number seems to be incremental based upon a global revision number, and NOT the actual revision number of the object being checked in.

If I'm creating a brand-new procedure and I check it in, the revision number should be 1??? Not 152 or some other number.

This way, after many changes, of when I want to go back to a prior version, you can easily find it!

Can this please be added?

8 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Serge shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Andrew Whitcomb commented  ·   ·  Report

    When you check in files to source control, you don't get to specify what version it uses - the source control system applies this number automatically. Most systems use a revision number that applies to everything in that source control root. So, this really doesn't have anything to do with RedGate Source Control. It has more to do with what source control system you use, and how you have it setup.

    This was a learning curve for us because we were used to VSS where each project used it's own revision level, but as we migrated items to TFS, everything switched to the root revision level.