Skip to content

Conversation

jelster
Copy link
Contributor

@jelster jelster commented Dec 20, 2016

When a database name along the lines of "WidgetCatalog_v8.3.433" is passed into the script, attach fails at the "v8.3". Rather than deal with trying to properly escape/encode a [ and ] around the names, I found that escaping them with quotes behaves as expected.

When a database name along the lines of "WidgetCatalog_v8.3.433" is passed into the script, attach fails at the "v8.3". Rather than deal with trying to properly escape/encode a `[` and `]` around the names, I found that escaping them with quotes behaves as expected.
@jelster
Copy link
Contributor Author

jelster commented Dec 20, 2016

If approved, it isn't a whole lot of effort to apply this change across the various SQL samples - would the preference be to do each in a separate PR or use a single for all of them?

@perrysk-msft
Copy link
Contributor

Thanks for the PR jelster! Please submit a single PR with the same code change for the rest of the Dockerfiles when you can.

@perrysk-msft perrysk-msft merged commit 9bdcd4b into microsoft:master Jan 5, 2017
@jelster
Copy link
Contributor Author

jelster commented Jan 7, 2017

No problem! I may have some other PR's I could send your direction involving the (UPDATE: I meant start.ps1) scripts -- since the Start.ps1 is pretty much the same do you want to follow this same pattern of creating 1 PR for review of a single sample, then creating separate PR for the rest, or would you prefer me to create a separate commit for each sample and send as a single PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants