I like Oracle SQL Developer. And I like TortoiseSVN. Oracle SQL Developer has versioning support, but some tasks are more easily done with TortoiseSVN. Maybe it’s what I’m accustomed to, but that’s the way I feel about it.
Today, I ran into a problem to get the versioning support in Oracle SQL Developer (based on SVNKit) to play nice with TortoiseSVN on the same working copy.
I have a repository on my harddrive and when I checked out files from within Oracle SQL Developer, TortoiseSVN refused to believe it was a legitimate subversion working copy. Vice versa, when checked out with TortoiseSVN, SQL Developer insisted that the directory was unversioned.
After a small investigation (I ran a diff on the .svn/entries files), the major difference was that TortoiseSVN used an uppercase C (“file:///C:/path/to/repos”) and Oracle SQL Developer used a lowercase c (“file:///c:/path/to/repos”). After I recreated the repository connection in Oracle SQL Developer with a capital C and checked out to a fresh working copy, TortoiseSVN was also convinced that it was indeed a subversion working copy.
I hope this tip will save you valuable time should you happen to run into the same problem.TortoiseSVN and Oracle SQL Developer,