Skip to content

Conversation

@roji
Copy link
Member

@roji roji commented Aug 1, 2022

Fixes #63630

@roji roji requested a review from ajcvickers August 1, 2022 11:23
@ghost ghost added the area-System.Data.Odbc label Aug 1, 2022
@ghost ghost assigned roji Aug 1, 2022
@ghost
Copy link

ghost commented Aug 1, 2022

Tagging subscribers to this area: @roji, @ajcvickers
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #63630

Author: roji
Assignees: -
Labels:

area-System.Data.Odbc

Milestone: -

{
// do not check string length if it was expanded because the final result may be shorter than the original
if ((null != connectionString) && (ODBC32.MAX_CONNECTION_STRING_LENGTH < connectionString.Length))
{ // MDAC 83536
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even know what this was? :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We tried finding out - for months (I can send you some email threads if you're really interested). One theory @GrabYourPitchforks had (based on other modifications in the changeset) was that this was a localization thing, i.e. that the P/Invoke call failed for long connection strings with some cryptic/non-localized error message, and that this check was added to surface a better error message. But we didn't manage to find a definitive answer.

@roji roji merged commit 8eb5dea into dotnet:main Aug 1, 2022
@roji roji deleted the Odbc1024 branch August 1, 2022 14:17
@ghost ghost locked as resolved and limited conversation to collaborators Aug 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support ODBC connection strings longer than 1024 characters

3 participants