You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We got into a strange scenario when we tried to test something against a copy of our database with a different database name.
Script run has hashes of post substituted scripts, which of course then failed as the tag substituted was a different database name. Causing RH to shout at us about an Up script being modified.
Would it be a sensible idea to record the script pre-substitution rather than post? This would obviously have a knock-on effect to existing users, so perhaps a flag to enable recording the pre-substituted version of the script?
I realise i am an edge case, feel free to tell me to "sod off"
The text was updated successfully, but these errors were encountered:
We got into a strange scenario when we tried to test something against a copy of our database with a different database name.
Script run has hashes of post substituted scripts, which of course then failed as the tag substituted was a different database name. Causing RH to shout at us about an Up script being modified.
Would it be a sensible idea to record the script pre-substitution rather than post? This would obviously have a knock-on effect to existing users, so perhaps a flag to enable recording the pre-substituted version of the script?
I realise i am an edge case, feel free to tell me to "sod off"
The text was updated successfully, but these errors were encountered: