Wrong specific version when using git source control
zbozic
Posts: 4 New member
in SQL Compare
Hi,
If I use Schema compare/deploy in MSSMS and try to compare current database with one chosen from git history, I got Specific version -1.
it seams that fetched history revision from git is wrong. (interestingly comment is fetched correctly).
That lead to if we pres button "compare/deploy with SQL compare" that we started external sql compare with wrong revision (-1) .
Furthermore this can not be used for comparison while this version does not exists.
BUT if I again search in standalone sql compare tool for needed version again - it pick it up correctly.
I use redgate source control version 6.0.2.6908 and SQL Compare 13.1.8.5525
Zelimir
If I use Schema compare/deploy in MSSMS and try to compare current database with one chosen from git history, I got Specific version -1.
it seams that fetched history revision from git is wrong. (interestingly comment is fetched correctly).
That lead to if we pres button "compare/deploy with SQL compare" that we started external sql compare with wrong revision (-1) .
Furthermore this can not be used for comparison while this version does not exists.
BUT if I again search in standalone sql compare tool for needed version again - it pick it up correctly.
I use redgate source control version 6.0.2.6908 and SQL Compare 13.1.8.5525
Zelimir
