Kbase P152144: Why doesn't a Dataset, when sent back to a .NET client, enable the .NET ChildKeyConstraint (i.e. Chi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/4/2009 |
|
Status: Unverified
GOAL:
Why doesn't a Dataset, when sent back to a .NET client, enable the .NET ChildKeyConstraint (i.e. ChildKeyConstraint.DeleteRule = Rule.Cascade)?
GOAL:
Why aren't .NET ChildKeyConstraints set when a DataSet is returned to .NET from the AppServer?
FACT(s) (Environment):
OpenEdge 10.x
Windows
FIX:
An ABL DataSet does not provide an automatic way to enforce parent->child constraints (i.e. when parent is deleted all children are automatically deleted). The ABL DataSet enables this functionality via a callback procedure so that the developer can implement whatever detailed constraint logic they desire). As a consequence of this, when passing a DataSet back to a .NET client there is no information available that would allow us to set the ChildKeyConstraint rules on the .NET side.
The developer should implement the needed ChildKeyConstraint rules within the .NET DataSet after it is returned from the AppServer.