Incorrect database name transliteration when connecting using WNET or XNET [CORE2561] #2971
Assignees
Comments
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 2 [ 10300 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @asfernandes
When connecting using WNET, the server was being recognized always as older than 2.5, causing the new database name transliteration algorithm to not work.
When connecting using XNET, that happens too, but is not important, because it's the same machine. But also with both protocols, the usage of # character was being passed to old servers that doesn't understand it.
Commits: 68ebf17
The text was updated successfully, but these errors were encountered: