title: Why doesn't Eclipselink generate the ON DELETE CASCADE clause in a unidirectional @ManyToOne relationship?
body: <p>These are two related entities in Eclipselink JPA:</p>
  
  <pre><code>@Entity
  public class Department {
  
      @Id
      @GeneratedValue(strategy = GenerationType.IDENTITY)
      private Long id;
  
      private String name;
  
  }
  
  @Entity
  public class Person {
  
      @Id
      @GeneratedValue(strategy = GenerationType.IDENTITY)
      private Long id;
  
      private String firstName;
  
      private String lastName;
  
      @ManyToOne(cascade={CascadeType.ALL})
      private Department department;
  
  }
  </code></pre>
  
  <p>and this is the generated DDL:</p>
  
  <pre><code>CREATE TABLE PERSON (ID BIGINT IDENTITY NOT NULL, FIRSTNAME VARCHAR, LASTNAME VARCHAR, DEPARTMENT_ID BIGINT, PRIMARY KEY (ID))
  CREATE TABLE DEPARTMENT (ID BIGINT IDENTITY NOT NULL, NAME VARCHAR, PRIMARY KEY (ID))
  ALTER TABLE PERSON ADD CONSTRAINT FK_PERSON_DEPARTMENT_ID FOREIGN KEY (DEPARTMENT_ID) REFERENCES DEPARTMENT (ID)
  </code></pre>
  
  <p>The environment is:
  - eclipselink 2.5.2
  - mysql-connector-java 5.1.6</p>
  
  <p>I would expect to have at least a ON DELETE CASCADE clause on the foreign key definition.
  What is the cascade option intended for, in the @ManyToOne relationship? 
  Do I really have to delete the children records manually before deleting the parent record?</p>