Activity overview
Latest activity by ecayer
I’m sorry to bring the news, but there isn’t a new version of Source Control for Oracle coming imminently.
We’d still like to hear from you about where you’re looking for this product to improve. We’re don’t assume that all capabilities in SQL Source Control should automatically be brought over to Source Control for Oracle, so the releases won’t go in lock-step. The up-side, though, is that gives us more flexibility to address needs specific to Oracle.
Warm regards,
Elizabeth Ayer
Portfolio Lead / comments
I’m sorry to bring the news, but there isn’t a new version of Source Control for Oracle coming imminently.
We’d still like to hear from you about where you’re looking for this product to im...
Hi Samot,
Yes, object locking can be used on a dedicated database. Are you sure that you’ve run the setup (found under the context menu ‘Other SQL Source Control tasks’) on your local machine? If so, then maybe check with support to figure out why you’re not seeing it on the context menu.
The locking will simply be on your local database, with no relation to other databases linked to the same repo. We considered trying to extend the feature to cover more dedicated use cases, but it just didn’t appear as important as for the shared-mode users, and in some cases can at least be done through the VCS. If we’ve got our prioritization wrong, we’re looking to you and others to set us right.
For the shared model of development, locking is an important capability – maybe even fundamental, as you say! Dedicated users will also get more than just a few bug fixes out of v4. SQL Source Control 4.0 is the start of the 4.x stream, which will deliver first-class Git connectivity and new platform support. If the 8 3.x releases were anything to go by, there will be plenty more to come.
Please keep telling us what you need.
Kind regards,
Elizabeth Ayer (Product Manager, SQL Source Control) / comments
Hi Samot,
Yes, object locking can be used on a dedicated database. Are you sure that you’ve run the setup (found under the context menu ‘Other SQL Source Control tasks’) on your local machin...
Hi, Andrew.
Caching in the add-in is something that isn't in the beta, but is scheduled to happen before the release. At this stage it's going to be limited to caching those messages that have been viewed, rather than allowing a full synchronisation on request, but that's on the cards for the future as well.
We have some more information for you about caching.
Unfortunately, Outlook caching of archived messages will not be available in the V1.0 release. We would love to have included it, but the time just doesn't allow for us both to implement it and test it to our satisfaction. Caching is still a high priority for us, though, for a follow-on release.
The up-side is that we now have a chance to talk through any specific requirements you may have related to caching. Please post this forum (or message me directly) to discuss further. / comments
Hi, Andrew.
Caching in the add-in is something that isn't in the beta, but is scheduled to happen before the release. At this stage it's going to be limited to caching those messages that have bee...