views:

701

answers:

3

I have a self-referential Role table that represents a tree structure

ID [INT] AUTO INCREMENT
Name [VARCHAR]
ParentID [INT]

I am using an ADO.NET DataTable and DataAdapter to load and save values to this table. This works if I only create children of existing rows. If I make a child row, then make a child of that child, then Update, the temporary ID value generated by the DataTable is going into the ParentID column. I have the following data relation set:

dataset.Relations.Add(New DataRelation("RoleToRole",RoleTable.Columns("ID"), RoleTable.Columns("ParentID")))

And when I make new child rows in the DataTable I call the SetParentRow method

newRow.SetParentRow(parentRow)

Is there something special I have to do to get the ID generation to propagate recursively when I call Update on the DataAdapter?

A: 

Does it make any difference if you go

newRow.SetParentRow(parentRow, RoleTable.Relations("RoleToRole"))
lomaxx
+1  A: 

I don't know ADO.net in particular, but most ORMs won't automatically insert the ID of a new record in a relationship. You'll have to resort to the 2-step process:

  1. build and save parent
  2. build and save child with relationship to parent

The reason that this is difficult for ORMs is because you might have circular dependencies, and it wouldn't know which object it needed to create an ID for first. Some ORMs are smart enough to figure out those relationships where there are no such circular dependencies, but most aren't.

James A. Rosen
ADO.NET is smart enough to push the parent ID into the child in a dataset when the parent is updated if there is a foreign key constraint set - so you need to save the parent before the child but not necessarily save the parent before you create the linked child. Not tried when self referential.
Murph
A: 

I suggest you add a ForeignKeyConstraint, with UpdateRule set to Cascade.

Joe