title: Not able to create foreign key constraint with on delete cascade as there is already one
body: <p>Below is the scenario</p>
  
  <ul>
  <li><p><code>Table1</code> (<code>Id, Name</code>)</p></li>
  <li><p><code>Table2</code> (<code>Id, Name1, Name2, Type</code>)</p>
  
  <ul>
  <li><code>FK1</code>: <code>Name1</code> references <code>Table1.Name</code> with <code>On delete cascade</code></li>
  <li><code>FK2</code>: <code>Name2</code> references <code>Table1.Name</code> with <code>On delete cascade</code></li>
  </ul></li>
  </ul>
  
  <p><code>FK2</code> throws the below error</p>
  
  <p>ERROR:</p>
  
  <blockquote>
    <p>Introducing FOREIGN KEY constraint FK2 on table Table2 may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.</p>
  </blockquote>
  
  <p>But, in my scenario whether the entity with <code>Name1</code> or <code>Name2</code> is deleted the corresponding entry in <code>Table2</code> should be deleted.</p>
  
  <p>Please help me understand what is the problem this could cause?</p>