Settings and activity
1 result found
We’re currently not planning to support this for v1. Would you be ok to remove the $id$ keyword for now?
We’ll have to see how many votes this suggestion gets…
Internal reference number: SOC-113Anonymous supported this idea ·
An error occurred while saving the comment
Did this functionality ever get implemented? I've just tried SQL Source Control v 220.127.116.11 and have the following problem:
1) Add keyword to stored procedure comment block
2) Commit change
3) SVN expands keyword post-commit
4) SQL Source Control doesn't update database with expanded keyword data
5) Immediately after committing change, SQL Source Control compares database to repo and sees the expanded keyword data as a change, so flags as a change that needs to be committed.
Repeat ad infinitum as the database copy is never updated and always contains the un-expanded keyword.
In addition, if I then try and change the stored procedure in the database, SQL Source Control sees the expanded keyword on the repo as a conflicting change and the universe implodes.
Basically, it's broken. Did I not set things up correctly?