[hibernate-issues] [Hibernate-JIRA] Updated: (ANN-632) @IndexColumn doesn't set value of index column

@IndexColumn doesn't set value of index column ---------------------------------------------- Key: ANN-632 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-632 Project: Hibernate Annotations Issue Type: Improvement Components: documentation Affects Versions: 3.3.0.ga Reporter: Dan Allen Assignee: Diego Pires Plentz Priority: Minor I'm sure I will get screamed at for this, but the @IndexColumn just doesn't work with @OneToMany. When I say it doesn't work, it means that I am a reasonable person and I have studied the documentation for at least 4 hours and I just cannot figure out how to make it work. So either the documentation needs to be improved, or there is something wrong with Hibernate. I refuse to believe that I am this stupid. Here is my problem in a nutshell. I have a Person and a collection of Jobs. The Jobs should be an indexed list based on the history that the person holds them. @Entity public class Person { @Id @GeneratedValue private long id; @Column private String name; @OneToMany(cascade=ALL, fetch=LAZY, mappedBy = "job") @IndexColumn(base = 1, name = "order") private List<Job> jobs = new ArrayList<Job>(); // getters and setters } @Entity public class Job { @Id @GeneratedValue private long id; @Column private String name; @ManyToOne @JoinColumn(name="person_id") private Person person; @Column private Integer order; // getters and setters } If I do the following, I get NULL for order. Person person = new Person(); person.setName("Chuck") Job job1 = new Job(); job1.setName("sysadmin") job1.setPerson(person); person.getJobs().add(job1); Job job2 = new Job(); jobs2.setName("network admin") job2.setPerson(person); person.getJobs().add(job2); entityManager.persist(person); Assume that the reason I am not assigning an order is more complex than this example. The point is that we want to see the order column populated with the index of the list. Now, if you give me the business about removing mappedBy, to that I will respond that by removing mappedBy, Hibernate tries to work with a person_job table, which I don't want. I want two tables, one for person and one for job.