Foreighn keys when deleting

Hi,
Using Ideablade 6.0.9.0 and INformix Dynamic Server 11.7

Let us first define tables for reproducing this problem:

TableA
   id_a serial not null privary key
   name varchar(50) not null

TableB
  id_b serial not null primary key
  id_a int   not null // foreighn key to Table A, cascade on delete
   name varchar(50) not null

TableC
  id_c serial not null primary key
  id_b int   not null // foreighn key to Table B cascaed on delete
   name varchar(50) not null

Let us say we have linked records in all 3 tables. If I via the EntityModel delete the record in TableA and save the results (by calling manager.SaveChangesAsync()) the records are deleted from table A, B an C as expected as the foreighn keys are "cascade on delete"

The strange thing is that if I instead delete the record from TableB, I get this error when I try to save:
Repository persistence operation failed; ERROR [23000] [IBM][IDS/NT32] Missing key in referenced table for referential constraint (informix.fk_tableC_2_tableB). (-111 ISAM error:  no record found.)

fk_tableC_2_tableB is the foreighn key based on id_b from table C to tabl B.

What on earth could be causing this?
Is the Entity Model doing something else than just:
  DELETE FROM TableB WHERE id_c = 22;
At least if I run such a SQL command from ServerStudio the record is deleted from TableB as well as the linked record in TableC.

Well no reply, talking to my self here :-)
Further investigation lead to that if Parent Entity (TableB) is having IsPendingEntityList = true for the list of child items in TableC everything works as supposed and there is only one record in e.Entities in the manager.Saving event with status Deleted

But as soon as that list is filled totally (IsPendingEntityList = true) things get wrong and the Entity Model deletes the entity in table B but then tries to modify the child entity in TableC in the same transaction. This is totally wrong and is a BAD BAD BUG.

Hi tj,

tj,