Skip to content
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

Add documentation for YesSQL breaking change #12681

Merged
merged 2 commits into from
Oct 25, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion src/docs/releases/1.5.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,4 +62,12 @@ ManageIndexes will be now ManageLuceneIndexes
|--------|--------|--------|
| Indexed | Indexed | Indexed meant "Keyword" in Lucene so we migrated these to "Keyword" in the content index settings.
| Analyzed | Keyword | The Analyzed option is removed. Everything that was set as analyzed doesn't need migration because it is now the default. |
| Stored | Stored | Nothing to do. Should work as before |
| Stored | Stored | Nothing to do. Should work as before |

## YesSQL breaking changes

YesSql is now using the new SQL client which encrypts the connection by default.

If the SQL Server does not have a trusted SSL certificate and you would and want to continue using encrypted communicated using the untrusted server, add `TrustServerCertificate=True` to the connection string.

If you do not want to encrypt the communication at all, you can use `Encrypt=false`.