Unexpected behaviour after rolling back in TFS

pcaston2pcaston2 Posts: 4 New member
in Automated Build and Release for Oracle
I made a change to my database, and source control detected it, and I checked it in. I went into TFS and rolled back the changes. My expectation at that point would be that source control for Oracle would again detectthe changes and offer to import them into TFS. It instead offered to update the SOURCE from the model with the delta. I understand this could be a use-case but seems odd. There was no mechanism to again treat the database as the source. I had to apply the changes to the DB then remake them to have SC for Oracle allow me to redploy it. Any way to get around this?
Tagged:
· Share on Twitter

Best Answer

Answers

  • David AtkinsonDavid Atkinson Posts: 1,458 Rose Gold 2
    I think you've responded to the wrong forum post! We're preparing a download link where you can get a build with the static data feature. Please bear with us.

    Regarding your question about rolling back changes in TFS, can I ask how you are linked to TFS? Are you using the TFS feature, or the Working Folder feature?
    David Atkinson
    Product Manager
    Redgate Software
    · Share on Twitter
Sign In or Register to comment.