Gabriel Bauman writes:
> Okay, so...
> > > name="child_id"
> > required="true"
> > primaryKey="true"
> > type="INTEGER"
> > autoIncrement="true"
> > />
> > > name="PARENT_TABLE_FK"
> > onDelete="cascade">
> ... given this example, if I delete or update the OM's ParentTable
> object, the associated records in CHILDTABLE should be deleted, right?
> Unfortunately, this does not work for me. The ParentTable record is
> deleted, but the children are not. Perhaps I need to tell the
> ParentTable instance to load its children explicitly? What am I missing?
What database are you using? PostgreSQL supports cascading deletes
nativly, but MySQL only does for InnoDB tables.... I believe that
Torque will silently ignore those options if the target database
doesn't support them.
+ "Were there monkeys? Some terrifying space monkeys maybe got loose?"