-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table: Characters encoded by our layer should be automatically decoded #257
Milestone
Comments
Should investigate what .NET does, to do they same thing they are doing. |
Candidate |
no longer applicable. |
sima-zhu
pushed a commit
to sima-zhu/azure-sdk-for-java
that referenced
this issue
Mar 21, 2019
* Add file request body * More rx adapter * Add more code * Implement shared channel pool * Functional impl of shared channel pool * Clean ups * Rename RxNetty -> Netty * Implement LRU for multi hash map * Fix checkstyle * add netty client & netty adapter * Merge and fix errors * Use an executor for pooling * Fix 1 core machine hanging * Checkstyle
mbhaskar
added a commit
to mbhaskar/azure-sdk-for-java
that referenced
this issue
Oct 31, 2019
Adding test to drain all the documents (Azure#257)
mbhaskar
added a commit
that referenced
this issue
Nov 6, 2019
* Enabling ignored query tests. * Porting query plan from v2 * Fixing failing tests Disabling non value aggregates * Porting offset limit support from V2 Adding test to drain all the documents (#257) * Fixing failing tests * Fixing failing tests
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If we put in illegal unicode chararacters, our table layer will encode those characters. But when retrieved, the user gets back not what they put in, but instead the encoding they didn't know about.
Things done by the layer should be automatically undone so the user neither knows nor cares.
For example:
Note that user stored the string "\u0005" (a single character, unicode code point 5), but what came back was the string
""
The text was updated successfully, but these errors were encountered: