null value with selfservicing and UnitOfWork when saving
Joined: 18-Nov-2006
Joined: 18-Nov-2006
Joined: 18-Nov-2006
I explain 
In DB I have:
Documento table: IDDocumento (PK) ... IDFiliale (FK -> Filiale table) ...
MovimentoMagazzino table: IDMovimentoMagazzino (PK) .... IDDocumento (FK -> Documento table) IDFiliale (FK -> Filiale table) ....
RigheDocumento table: IDRigaDocumento (PK) IDocumento (FK -> Documento table) .....
in DocumentoManager, before saving i have this scenario (where doc is a DocumentoEntity instance) :
doc.RigheDocumenti.Count = 2;
next:
MovimentoMagazzinoEntity movimento;
foreach (RigaDocumentoEntity riga in doc.RigheDocumento)
{
movimento = new MovimentoMagazzinoEntity();
movimento.IDFiliale = doc.IDFiliale;
...........
doc.MovimentoMagazzino.Add(movimento);
}
uow.AddForSave(doc,true);
I start debugging using runtime library source code ... so i noticed that when it builds the 2th INSERT INTO query of MovimentoMagazzinoEntity (because doc.MovimentoMagazzino.Count =2, and there was 2 entity to insert) when it executes the method:
protected virtual bool CheckIfFieldNeedsInsertAction(IEntityFieldCore field)
inside it field.IsChanged (when field.Name is "IDFiliale") becomes false.. So it skips the IDFiliale parameter during the second query building.
I think that this appens due to "foreach" that use the same "movimento" variable. Is this possible?
DDL SQL:
CREATE TABLE [dbo].[Documenti] (
[IDDocumento]int IDENTITY(1, 1) NOT NULL,
..............
[IDFiliale]int NOT NULL,
.................
CONSTRAINT [Documenti_PK] PRIMARY KEY CLUSTERED ([IDDocumento]),
...............
CONSTRAINT [Filiali_Documenti_FK1] FOREIGN KEY ([IDFiliale])
REFERENCES [dbo].[Filiale] ([IDFiliale])
ON UPDATE NO ACTION
ON DELETE NO ACTION,
........................
)
ON [PRIMARY]
TEXTIMAGE_ON [PRIMARY]
GO
CREATE TABLE [dbo].[RigheDocumenti] (
[IDRigaDocumento]int IDENTITY(1, 1) NOT NULL,
[IDDocumento]int NOT NULL,
............
CONSTRAINT [RigheDocumenti_PK] PRIMARY KEY CLUSTERED ([IDRigaDocumento]),
CONSTRAINT [Documenti_RigheDocumenti_FK1] FOREIGN KEY ([IDDocumento])
REFERENCES [dbo].[Documenti] ([IDDocumento])
ON UPDATE CASCADE
ON DELETE CASCADE,
.............
)
ON [PRIMARY]
GO
CREATE TABLE [dbo].[MovimentiMagazzino] (
[IDMovimentoMagazzino]int IDENTITY(1, 1) NOT NULL,
[IDFiliale]int NOT NULL,
[IDDocumento]int NULL,
.......
CONSTRAINT [MovimentiMagazzino_PK] PRIMARY KEY CLUSTERED ([IDMovimentoMagazzino]),
CONSTRAINT [Documenti_MovimentiMagazzino_FK1] FOREIGN KEY ([IDDocumento])
REFERENCES [dbo].[Documenti] ([IDDocumento])
ON UPDATE CASCADE
ON DELETE NO ACTION,
.....
CONSTRAINT [Filiali_MovimentiMagazzino_FK1] FOREIGN KEY ([IDFiliale])
REFERENCES [dbo].[Filiale] ([IDFiliale])
ON UPDATE NO ACTION
ON DELETE NO ACTION,
)
ON [PRIMARY]
TEXTIMAGE_ON [PRIMARY]
GO
braidiano wrote:
I explain
In DB I have:
Documento table: IDDocumento (PK) ... IDFiliale (FK -> Filiale table) ...
MovimentoMagazzino table: IDMovimentoMagazzino (PK) .... IDDocumento (FK -> Documento table) IDFiliale (FK -> Filiale table) ....
RigheDocumento table: IDRigaDocumento (PK) IDocumento (FK -> Documento table) .....
in DocumentoManager, before saving it does this operations:
MovimentoMagazzinoEntity movimento; foreach (RigaDocumentoEntity riga in doc.RigheDocumento) { movimento = new MovimentoMagazzinoEntity(); movimento.IDFiliale = doc.IDFiliale; ........... doc.MovimentoMagazzino.Add(movimento); } uow.AddForSave(doc,true); where [b]doc[/b] is a DocumentoEntity instance.
At the point where movimento.IDFiliale = doc.IDFiliale is set, it's true that doc.IDFiliale has a value and is changed? As the exception shows that the FK field IDFiliale in doc is null (not saved)
I start debugging using runtime library source code ... so i noticed that when it builds the 2th INSERT INTO query of MovimentoMagazzinoEntity (because doc.MovimentoMagazzino.Count =2, and there was 2 entity to insert) when it executes the method:
protected virtual bool CheckIfFieldNeedsInsertAction(IEntityFieldCore field)inside it field.IsChanged (when field.Name is "IDFiliale") becomes false.. So it skips the IDFiliale parameter during the second query building.
I find that hard to believe:
/// <summary>
/// Checks the if field needs insert action.
/// </summary>
/// <param name="field">Field.</param>
/// <returns>true if the field needs to be included in the insert query. This is the case if the field is
/// changed or not read only, or that it is linked to a supertype field (which indicates that the field will be receiving its value later)</returns>
protected virtual bool CheckIfFieldNeedsInsertAction(IEntityFieldCore field)
{
// needs insert action when:
// - field is changed
// - field is not readonly
// - field is linked to a supertype field
// - field is a discriminator column
return ( (!field.IsReadOnly && field.IsChanged) || (field.LinkedSuperTypeField!=null) || field.GetDiscriminatorColumnFlag());
}
i.w.o. it doesn't change anything.
The field's IsChanged flag is set to false after the entity has been inserted (but that's after the insert was executed)
I think that this appens due to "foreach" that use the same "movimento" variable. Is this possible?
No that's not the problem. Please check if you set in the doc instance the Field mapped onto the relation Documento -> Filiale to an instance of Filiale.
Joined: 18-Nov-2006