API Proposal: `HasOnDeleteSetNullProperties()` to support Postgres 15+ `ON DELETE SET NULL (column_a, column_b)` column lists
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 45/100
Direzione di ricerca
Start by reading the Npgsql annotation provider and migrations SQL generator, especially their foreign-key constraint handling; the issue’s prototype shows the intended integration points but does not name repository file paths or tests. Check existing tests for foreign-key migration SQL and annotation handling, then add coverage for the proposed property- and column-based APIs. Done means generated migrations include the selected column list for SET NULL or SET DEFAULT.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Preface
PostgreSQL 15+ added support for specifying a list of columns after a ON DELETE SET NULL or ON DELETE SET DEFAULT constraint, which specifies which subset of a composite foreign key's columns to set to NULL when the principal is deleted, instead of all columns in the foreign key.
The DDL constraints documentation states:
The actions SET NULL and SET DEFAULT can take a column list to specify which columns to set. Normally, all columns of the foreign-key constraint are set; setting only a subset is useful in some special cases.
For example:
FOREIGN KEY (tenant_id, author_id) REFERENCES users ON DELETE SET NULL (author_id);
Npgsql does not yet support a built-in way to target specific SET NULL columns using the standard Fluent API.
Proposed API
An extension method for ReferenceCollectionBuilder named HasOnDeleteSetNullColumns() for specifying raw column names, and HasOnDeleteSetNullProperties() for the property names, with overloads for string array and lambda expression:
public static ReferenceCollectionBuilder HasOnDeleteSetNullColumns(
this ReferenceCollectionBuilder builder,
params string[] setNullColumnNames)
public static ReferenceCollectionBuilder HasOnDeleteSetNullProperties(
this ReferenceCollectionBuilder builder,
params string[] setNullPropertyNames)
public static ReferenceCollectionBuilder<TPrincipalEntity, TDependentEntity> HasOnDeleteSetNullProperties<TPrincipalEntity, TDependentEntity>(
this ReferenceCollectionBuilder<TPrincipalEntity, TDependentEntity> builder,
Expression<Func<TDependentEntity, object?>> setNullPropertiesExpression)
where TPrincipalEntity : class
where TDependentEntity : class
Example usage
modelBuilder.Entity<Author>()
.HasMany(a => a.Posts)
.WithOne(p => p.Author)
.HasPrincipalKey(a => new { a.TenantId, a.Id })
.HasForeignKey(p => new { p.TenantId, p.AuthorId })
.OnDelete(DeleteBehavior.SetNull)
.HasOnDeleteSetNullProperties(p => p.AuthorId);
// or .HasOnDeleteSetNullProperties("AuthorId");
// or .HasOnDeleteSetNullColumns("author_id");
Workarounds
Current workarounds include manually modifying the migrations with custom SQL to drop the initial constraint and re-add it with the column list, or to manually extend the migration generator. The latter being the path I took to prototype an implementation of this proposal, which may serve as the basis for a future PR.
This prototype implements:
- Two custom annotations:
- "CustomNpgsql:OnDeleteSetNull:PropertyNames" is the property name list
- "CustomNpgsql:OnDeleteSetNull:ColumnNames" is the actual column name list
ReferenceCollectionBuilderextension methods- Adds the annotations to the Foreign Key Constraint
- Derived
NpgsqlAnnotationProvider- Translates "CustomNpgsql:OnDeleteSetNull:PropertyNames" into concrete column names and re-adds them into the relational model as "CustomNpgsql:OnDeleteSetNull:ColumnNames"
- Yields existing "CustomNpgsql:OnDeleteSetNull:ColumnNames" to the relational model
- Derived
MigrationsSqlGenerator- Adds on the additional column list SQL during ForeignKeyConstraint generation
Extension methods
public static ReferenceCollectionBuilder HasOnDeleteSetNullColumns(
this ReferenceCollectionBuilder builder,
params string[] setNullColumnNames)
{
builder.HasAnnotation(
"CustomNpgsql:OnDeleteSetNull:ColumnNames",
setNullColumnNames);
return builder;
}
public static ReferenceCollectionBuilder HasOnDeleteSetNullProperties(
this ReferenceCollectionBuilder builder,
params string[] setNullPropertyNames)
{
builder.Metadata.SetAnnotation(
"CustomNpgsql:OnDeleteSetNull:PropertyNames",
setNullPropertyNames);
return builder;
}
public static ReferenceCollectionBuilder<TPrincipalEntity, TDependentEntity> HasOnDeleteSetNullProperties<TPrincipalEntity, TDependentEntity>(
this ReferenceCollectionBuilder<TPrincipalEntity, TDependentEntity> builder,
Expression<Func<TDependentEntity, object?>> setNullPropertiesExpression)
where TPrincipalEntity : class
where TDependentEntity : class
{
string[] setNullPropertyNames = setNullPropertiesExpression
.GetMemberAccessList()
.Select(member => member.Name)
.ToArray();
builder.Metadata.SetAnnotation(
"CustomNpgsql:OnDeleteSetNull:PropertyNames",
setNullPropertyNames);
return builder;
}
Custom NpgsqlAnnotationProvider
public class CustomNpgsqlAnnotationProvider : NpgsqlAnnotationProvider
{
public CustomNpgsqlAnnotationProvider(RelationalAnnotationProviderDependencies dependencies)
: base(dependencies)
{
}
public override IEnumerable<IAnnotation> For(IForeignKeyConstraint foreignKeyConstraint, bool designTime)
{
foreach(IAnnotation baseAnnotion in base.For(foreignKeyConstraint, designTime)) {
yield return baseAnnotion;
}
foreach (IForeignKey thisForeignKey in foreignKeyConstraint.MappedForeignKeys)
{
if (thisForeignKey.FindAnnotation("CustomNpgsql:OnDeleteSetNull:ColumnNames")?.Value is string[] columnNames)
{
yield return new Annotation(
"CustomNpgsql:OnDeleteSetNull:ColumnNames",
columnNames
);
}
// Translate CustomNpgsql:OnDeleteSetNull:PropertyNames -> CustomNpgsql:OnDeleteSetNull:ColumnNames
if (thisForeignKey.FindAnnotation("CustomNpgsql:OnDeleteSetNull:PropertyNames")?.Value is string[] propertyNames)
{
// Translate property names to column names using the set of columns from the foreign key constraint
string[] columnNames = propertyNames
.SelectMany(p =>
foreignKeyConstraint.Columns
.Where(c => c.PropertyMappings.Any(pm => pm.Property.Name == p))
)
.Select(c => c.Name)
.ToArray();
yield return new Annotation(
"CustomNpgsql:OnDeleteSetNull:ColumnNames",
columnNames
);
}
}
}
}
Custom NpgsqlMigrationsSqlGenerator
public class CustomNpgsqlMigrationsSqlGenerator : NpgsqlMigrationsSqlGenerator {
protected override void ForeignKeyConstraint(AddForeignKeyOperation operation, IModel? model, MigrationCommandListBuilder builder)
{
// Write the constraint as standard. This is not yet terminated.
base.ForeignKeyConstraint(operation, model, builder);
// Only append column list to SET NULL or SET DEFAULT
if (operation.OnDelete is ReferentialAction.SetNull or ReferentialAction.SetDefault
&& operation?.FindAnnotation("CustomNpgsql:OnDeleteSetNull:ColumnNames")?.Value is string[] columnNames && columnNames.Length > 0)
{
// Append the column list
builder.Append(" (");
builder.Append(ColumnList(columnNames));
builder.Append(")");
}
}
}
- Lingua principale
- C#
- Stelle
- 1.8k
- Fork
- 268
- Merge medio
- 2h 35m
- PR unite (30g)
- 136
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di npgsql/efcore.pg
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
NTS: the M ordinate is dropped from geometry SQL literals and from geometries stored in JSONForse già presa @Ahmed7991 l’ha presa 5 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
npgsql/efcore.pg#4093 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
`TimeSpan`/`Duration` component members: negative values are floored, and intervals computed in SQL are read field by fieldForse già presa @jeremy-morren l’ha presa 11 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
Numeric storage parameters are formatted with the current culture, so migrations emit 0,01 instead of 0.01Forse già presa @Sorbitol l’ha presa 12 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 30/100
I maintainer di solito rispondono entro 1 giorno
-
`Contains` on a JSON primitive collection compares JSON text, so `DateTime` and `TimeOnly` items never matchForse già presa @Mr444-dev l’ha presa 7 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
npgsql/efcore.pg#4099 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di npgsql/efcore.pg
Issue simili
-
Issue-Bug Needs-Triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
JiaFeiMiao-K-Cat/DiscImageStudio#281 ·
I maintainer di solito rispondono entro 1 giorno
-
area/access-management Frontend onboarding candidate :handshake:
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
Altinn/altinn-auth#4941 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
aws/aws-sdk-net#4586 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Kryptos-FR/MarkView.Avalonia#269 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno