You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now any time this converter is used, the database column will be non-unicode with a max length of 20. However, these are only hints since they are be overridden by any facets explicitly set on the mapped property.
I suspect "are be overridden" should be "could be overridden"?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 03dfe9f6-e831-ac3f-0b90-acb9b4c0f828
Version Independent ID: a26156d1-a4b3-7df0-e63e-b8e9f804abbf
I believe I've spotted a grammatical error in the following paragraph in the 'Column facets and mapping hints' section on the Value Conversions page:
Now any time this converter is used, the database column will be non-unicode with a max length of 20. However, these are only hints since they are be overridden by any facets explicitly set on the mapped property.
I suspect "are be overridden" should be "could be overridden"?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: