Skip to content

Add Integrated Security connstring param removal to the 8.0 breaking changes list #387

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.

Sign up for GitHub

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

Merged
roji merged 1 commit into from
Jan 20, 2025
Merged

Add Integrated Security connstring param removal to the 8.0 breaking changes list #387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions conceptual/Npgsql/release-notes/8.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,7 @@ As part of improving Npgsql's support for the PostgreSQL network mappings (see a

### Obsoletions and obsolete API removals

* The `Integrated Security` connection parameter has been removed. It was never actually necessary - simply stop setting it.
* `NpgsqlTsVector.Parse()` and `NpgsqlTsQuery.Parse()` are now obsolete. These methods attempted to mimic the behavior of the PostgreSQL `to_tsvector` and `to_tsquery` functions, but could only do so partially and in problematic ways. Use the PostgreSQL functions instead.
* The parsing functions on the built-in geometry types (NpgsqlPoint, NpgsqlBox etc.) have been removed; similarly, they partially replicated PostgreSQL parsing functionality client-side and had issues.
* `NpgsqlLargeObjectManager` and `NpsgqlLargeObjectStream` are now obsolete. These types were very rarely-used, provided only a thin wrapper over easily-accessible PostgreSQL large-object functions, and limited usage in various ways (e.g. they didn't allow batching). Call the PostgreSQL large-object functions directly.
Expand Down