Skip to content

Settings and activity

1 result found

  1. 530 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Kendra responded

    Thanks for this suggestion and for the many comments and upvotes. I realize that this is a pain point.

    I have a few shorter-term workarounds to summarize as well as some information on the longer roadmap in this update. I know these shorter-term workarounds aren’t perfect (I summarize the pros and cons), but I’m posting them as they may help a few folks.

    Workaround 1) When data changes to static data need to be made, use a “relink the table” pattern
    One can “cleanly rescript” a static data table in SQL Source Control by:

    • Unlinking the static data table
    • Committing
    • Relinking the static data table
    • Committing

    Pro: This works with the GUI and requires no special knowledge or comfort with TSQL. This may help folks with just a few static data tables.
    Con: This requires extra steps and results in extra commits in the history, which I realize can…

    An error occurred while saving the comment
    Philippe Dansereau commented  · 

    I'm currently achieving that feature thru some contortions: When order gets mixed up by RGSS, I use Red Gate Data compare to compare my branch and an empty db. I then ask data compare for a script. It complies and gives me a nicely ordered script that I then cut & paste back in my version control x_Data.sql file. So, since Data Compare can do it, it should be easy to add the feature in RGSS, I hope.

    Philippe Dansereau supported this idea  ·