Comments
Sort by recent activity
We've fixed this bug in today's release (0.0.3.463). It will now only enable the clean build option for builds that use our runner, leaving all other builds untouched. You can download the fixed build from: http://downloads.red-gate.com/EAP/openMe/openMe.zip
Let us know if you have any further problems,
David / comments
We've fixed this bug in today's release (0.0.3.463). It will now only enable the clean build option for builds that use our runner, leaving all other builds untouched. You can download the fixed ...
If you mean renaming the database on SQL server, then the best way is:
1. make sure that both the commit tab and the get latest tab are empty by committing all your outstanding changes and gettting all of your teammates
2. on the setup tab, right-click on the URL where it's linked to and click copy
3. on the setup tab, unlink the database from source control
4. rename the database
5. on the setup tab, link it to the same location (you can paste the URL that you copied above)
6. visit the commit tab and wait for the spinny to finish (you should see the spinny say "Accepting updates from source control" which is where it determines that your database is already fully up-to-date with no changes to commit or get, and we sort out our internal data structures to reflect this)
At this point you should be done. Let me know if you have any problems. / comments
If you mean renaming the database on SQL server, then the best way is:
1. make sure that both the commit tab and the get latest tab are empty by committing all your outstanding changes and gettting...
Our internal builds are currently using a daily build of SharpSvn that is built again SVN 1.7. It's looking pretty good at the moment (there's 1 outstanding known issue that we need to fix), so it's highly likely that the next Early Access release of 3.0 will have it (unfortunately it didn't make the Early Access release that went out earlier today). / comments
Our internal builds are currently using a daily build of SharpSvn that is built again SVN 1.7. It's looking pretty good at the moment (there's 1 outstanding known issue that we need to fix), so it...
Cool!
Having a button/menu item to fix the working base is not something that's easy for us to do right now in v2, but for v3 we're planning to add an extended property to the database so that we know what revision it is at.
When you restore the backup, we could spot that the revision has gone back in time, and so fix the working base for you automatically, without a need for a button/menu item. I'll raise this with our product manager and see what he thinks. We're on a quite tight release schedule for v3, so if we do decide to do it, it'll be more likely to be done after that point, i.e. v3.1 at the earliest. / comments
Cool!
Having a button/menu item to fix the working base is not something that's easy for us to do right now in v2, but for v3 we're planning to add an extended property to the database so that we k...
I'm one of the developers on SQL Source Control, and I just thought I'd explain a little more in depth what's going on.
When you restore the database backup (which essentially takes your local database back in time), SQL Source Control doesn't know that you've done that specific action. All it knows is that your local database has been changed. Therefore, the retrieve tab will be empty (as you observed, because the SVN repository hasn't changed, so there's nothing to retrieve), and the commit tab will show all the changes that restoring the backup has made to the database. These changes can then be committed (on the commit tab), or undone (on the undo dialog). Alternatively you can unlink and relink which will give you a new "Working Base", with the effects that you observed.
If you just want to see the differences the commit tab is the easiest way to do it, but it's very confusing to look at (because the changes are the wrong way round). You can then use commit button to change the SVN repo to be the state of the backup, or you can use undo to change the database to be the state of the repository. Why both of these work is quite confusing UX though, so we recommend unlinking and re-linking.
The workaround Pete gave of deleting the offending files from the working base isn't quite right. Instead for step 2 you need to use TortoiseSVN to update the working base to the SVN revision that the database backup corresponds to. The reason why deleting the offending files won't work is that SQL Source Control will notice that they're missing, and automatically put the files back again, which isn't what you want. / comments
I'm one of the developers on SQL Source Control, and I just thought I'd explain a little more in depth what's going on.
When you restore the database backup (which essentially takes your local data...
Aah, that would explain it. Can you please give me the details for how you've configured vim to be your text editor, so that I can reproduce the issue here and looking into fixing it.
Thanks! / comments
Aah, that would explain it. Can you please give me the details for how you've configured vim to be your text editor, so that I can reproduce the issue here and looking into fixing it.
Thanks!
I've tried to reproduce this on my machine and at the step you mentioned Notepad is correctly launched so that a new commit message can be entered. When I entered a new commit message in Notepad, saved the file, and closed Notepad, the commit in SQL Source Control finished successfully.
Can I just double-check with you that Notepad definitely isn't launched? On my machine it was set to be the active window, but can you please carefully check to see if it was launched, but because it wasn't made the active window you didn't notice it.
It is mercurial itself that is launching Notepad (SQL Source Control just asks mercurial to do the commit, and it decides to launch Notepad), so is there any chance you could have configured mercurial not to launch Notepad? This setting could be in the hg command line or in TortoiseHg. / comments
I've tried to reproduce this on my machine and at the step you mentioned Notepad is correctly launched so that a new commit message can be entered. When I entered a new commit message in Notepad, ...
Hi Chris,
I'm one of the developers on SQL Source Control.
You can safely ignore all of the SQL Source Control errors.
In order to help us fix bugs, SQL Source Control logs a vast amount of information.
The first two (Unhandled Exception: Thread was being aborted.. IsTerminating : False) are because SQL Source Control logs any errors in any SSMS add-ins, and in this case, they aren't SQL Source Control bugs, but are the SQL Prompt error that Paul has already talked about.
The final one (An exception occurred whilst logging the start of day information: System.UnauthorizedAccessException: Access is denied) is caused because we try to log information about disk quota, and we can't access this information (either because you aren't an administrator, or because UAC is enabled). We try to log disk quota in order to help us diagnose bugs where SQL Source Control goes wrong because the user has run out of disk quota.
Cheers,
David / comments
Hi Chris,
I'm one of the developers on SQL Source Control.
You can safely ignore all of the SQL Source Control errors.
In order to help us fix bugs, SQL Source Control logs a vast amount of informa...
So the thing that would be easiest for me is if I could reproduce your problem here. Would you be able to send me a copy of all of the HTTPS certificates in the chain? This will enable me to create a very similar certificate chain here, and easily debug the issue.
The following instructions will let you save the HTTPS certificate chain from Firefox 3.6.3, but hopefully they should be fairly similar for other versions:
1. Connect to the relevant server, e.g. by putting https://server/ in the address bar, and pressing enter.
2. After the page has loaded, right-click somewhere on the page.
3. Left-click the View Page Info menu item.
4. Left-click the Security tab.
5. Left-click the View Certificate button.
6. Left-click the Details tab.
7. For each one of the certificates in the Certificate Hierarchy, left-click on it to select it, and then click the Export button; the default file name should be fine, so just click the Save button.
You should now have several files, one for each one of the certificates in the Certificate Hierarchy.
If you could email me all of the files, david.simner@red-gate.com, that would be awesome [image] / comments
So the thing that would be easiest for me is if I could reproduce your problem here. Would you be able to send me a copy of all of the HTTPS certificates in the chain? This will enable me to crea...
The error message from SQL Source Control means that it does not trust the SSL certificate that your Subversion server uses. Given the circumstances you describe ("signed by an internal CA") I would guess that this is because SQL Source Control doesn't know that your internal CA should be trusted.
Can I ask what web browser it works fine in?
SQL Source Control should trust all the SSL certificates that Internet Explorer trusts, so if the answer is Internet Explorer, then this is an unknown bug, and I'd very much like to work with you to understand and fix what is causing it to go wrong.
If the answer is not Internet Explorer (e.g. Firefox, Chrome, Safari, etc), then unfortunately at this time, SQL Source Control does not trust all the SSL certificates that they trust, and so I would expect the behaviour that you observed to occur. As a workaround, until we've fixed this, you can either: (1) click the OK button, or (2) configure Internet Explorer to trust your internal CA's SSL certificate.
Looking forward to hearing from you,
David / comments
The error message from SQL Source Control means that it does not trust the SSL certificate that your Subversion server uses. Given the circumstances you describe ("signed by an internal CA") I wou...