Fix #87 by working around non-federated sqlproxy connections #89
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
graysonarts
pushed a commit
that referenced
this pull request
Oct 7, 2016
When Cross Database Joins were introduced in 10 all connections became "federated" by default, even if they weren't actually joined to anything else. In the file format that means they get represented as named-connection/connection elements. Expressed under one top-level connection element with a class of 'federated'. Except for 'sqlproxy' connections (Published Data Sources) -- they stay in the old connection style as a top level connection element. We need to, when in a 10.0 or greater workbook, get all federated connections (named-connection) plus go back and find any sqlproxy connections as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #87
'sqlproxy' connections can't be federated yet so they exist outside the 'named-connections' groupings that all other connections live in.
The simplest change is to just grab all federated connections and then make a second pass to get the published datasource connections too.
Added a test to verify the case with a mixed-case workbook: Federated and Non-Federated connections