(Kodo 4.1); DELETE issued even with @ForeignKey cascade delete?

Question

I'm wondering if anyone has seen this.
I'm using Kodo 4.1, and MySQL, and I basically have the following situation (default generated IDs omitted):
Code:
@Entity
public class A {
  @OneToMany(mappedBy="a", cascade=CascadeType.ALL, fetch=FetchType.EAGER)
  private Set<BB> bMany = new HashSet<BB>();
@Entity
public class BB {
@ManyToOne(cascade={CascadeType.PERSIST, CascadeType.REFRESH })
@JoinColumn(name = "A_ID")
@ForeignKey(deleteAction=ForeignKeyAction.CASCADE)
private A a;
Schema:
CREATE TABLE BB(
  A_ID BIGINT NOT NULL,
  CONSTRAINT FOREIGN KEY (A_ID) REFERENCES A(ID) ON DELETE CASCADE
) ENGINE=InnoDB;OK. I create an A with a couple of BBs in it, and persist it. Everything's fine. Now I call entityManager.remove() on the A instance I persisted, and I can see it issuing DELETE commands for BB after the DELETE for A, which produces an OptimisticLockException. I'd have hoped that the above @ForeignKey would have told Kodo not to issue such commands, knowing that the DB would do it.
Any insight? Have I used @ForeignKey correctly (examples seem sparse in the documentation)? Is there a workaround, other than removing the cascade delete and doing deletions manually from code?
Thanks,
-- Bryan Loofbourrow

Answer 1

1. Kodo needs to know the constraints set on mapped columns.
Set the following properties in your configuration
kodo.jdbc.SchemaFactory:native(ForeignKeys=true)
2. Are you explictly setting kodo.jdbc.UpdateManager property?