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

Merge 3.8.x up into 4.0.x #6487

Merged
merged 5 commits into from
Aug 7, 2024
Merged

Merge 3.8.x up into 4.0.x #6487

merged 5 commits into from
Aug 7, 2024

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Aug 7, 2024

No description provided.

stof and others added 5 commits August 6, 2024 17:19
Without this change, the schema comparison will not remove existing type
comments when disabling them because it will still silently remove that
part of the comment during introspection (and so won't detect an
expected change between the expected empty comment and the introspected
comment).
Disabling that stripping logic when disabling type comments corresponds
to the behavior of DBAL 4 regarding comments, which is exactly what the
configuration option is about.
2 things need to change:

- the path to the binary, which is now secure by default;
- the addition of the -C flag, telling sqlcmd to trust the certificate
  of the server.

Quote from the documentation:

> In SQL Server 2022 (16.x) CU 14 and later versions, container images
> include the new mssql-tools18 package. The previous directory
> /opt/mssql-tools/bin is being phased out. The new directory for
> Microsoft ODBC 18 tools is /opt/mssql-tools18/bin, aligning with the
> latest tools offering. For more information about changes and security
> enhancements, see https://techcommunity.microsoft.com/t5/sql-server-blog/odbc-driver-18-0-for-sql-server-released/ba-p/3169228

See microsoft/mssql-docker#892
Adapt to mssql-docker breaking change
Make the schema manager aware of the disabling of type comments
@greg0ire greg0ire merged commit 3892303 into doctrine:4.0.x Aug 7, 2024
75 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants