title: Hibernate Many-To-One Relationship without Foreign Key but with reverse foreign key
body: <p>I have the following DB:</p>
  
  <pre><code>CREATE TABLE car_owner (
    car_owner_id int(11) NOT NULL,
    car_id_fk int(11) DEFAULT NULL,
    PRIMARY KEY (car_owner_id),
    KEY car_owner_car_fk_idx (car_id_fk),
    CONSTRAINT car_owner_car_fk FOREIGN KEY (car_id_fk) REFERENCES car (car_id) ON DELETE NO ACTION ON UPDATE NO ACTION,
  ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
  
  
  CREATE TABLE car (
     car_id int(11) NOT NULL AUTO_INCREMENT,
     car_type varchar(45) DEFAULT NULL,
     car_plates varchar(25) DEFAULT NULL,
    PRIMARY KEY (car_id),
  ) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1;
  </code></pre>
  
  <p>And In the java model:</p>
  
  <p>For CarOwner I have:</p>
  
  <pre><code>@Entity
  @Table(name="car_owner")
  @NamedQuery(name="CarOwner.findAll", query="SELECT co FROM CarOwner co")
  public class CarOwner implements Serializable {
  
      @Id
      @GeneratedValue
      @Column(name="car_owner_id")
      private Integer carOwnerId;
  .....
  
      //bi-directional many-to-one association to Car
      @OneToMany(fetch = FetchType.EAGER)
      @JoinColumn(name = "car_id_fk", referencedColumnName = "car_id")
      private List&lt;Car&gt; cars;
  </code></pre>
  
  <p>And for Car:</p>
  
  <pre><code>@Entity
  @Table(name="car")
  @NamedQuery(name="Car.findAll", query="SELECT c FROM Car c")
  public class Car implements Serializable {
  
      @Id
      @GeneratedValue
      @Column(name="car_id")
      private Integer carId;
  ......
  
      //bi-directional many-to-one association to car_owner
      @ManyToOne(fetch=FetchType.EAGER)
      @JoinColumn(name = "car_owner_id")
      private CarOwner carOwner;
  </code></pre>
  
  <p>The problem here is that Hibernate can't relate the tables and goes creating new <code>car_id</code> and <code>car_owner_id</code> columns in car table automatically.</p>
  
  <p>Can anybody help in finding the right combination in the model to relate the tables appropriately.</p>