Skip to content

docs: the README's known defects are the two that are open #140

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
CaffeinatedCoder merged 1 commit into from
Nov 14, 2026
Merged

docs: the README's known defects are the two that are open #140

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
6 changes: 0 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,12 +101,6 @@ Known defects of this preview, each with what it costs:
class for arrays ([#104](https://github.com/CaffeinatedCoder/CodoMetis.EFCore.SchemaKit/issues/104)).
- A table moved back to the default schema stays in its old schema on Npgsql, with its constraints
([#105](https://github.com/CaffeinatedCoder/CodoMetis.EFCore.SchemaKit/issues/105)).
- A constraint renamed in place frees its name after EF Core's operations, so an index created
under that name in the same migration fails with `42P07`
([#99](https://github.com/CaffeinatedCoder/CodoMetis.EFCore.SchemaKit/issues/99)).
- Two objects of one name, one on a table without a schema and one on a table in `public`, are
not refused as a collision, and the migration fails at apply with `42P07`
([#100](https://github.com/CaffeinatedCoder/CodoMetis.EFCore.SchemaKit/issues/100)).

## Which package for which EF Core

Expand Down
Loading