9:14 a.m.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Dan Allen commented on ANN-632:
-------------------------------
Okay, I at least figured out how to get it to assign the order column. Here are the
updated entities that do in fact work.
@Entity
public class Person {
@Id @GeneratedValue
private long id;
@Column
private String name;
@OneToMany(cascade=ALL, fetch=LAZY)
@IndexColumn(base = 1, name = "order")
@JoinColumn(name="person_id", nullable=false)
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", insertable=false, updatable=false,
nullaable=false)
private Person person;
@Column(insertable=false, updatable=false)
private Integer order;
// getters and setters
}
However, the only problem now is that when I retrieve the Jobs from the database, the
order is always NULL, even though it is NOT NULL in the database. So clearly the writes
are now working, but the reads are still screwy.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Dan Allen commented on ANN-632:
-------------------------------
At long last, I am down to the real problem. So everything above is much needed
documentation. What is in this comment is the real crux.
The only way that I see the order on the Job object within the same persistence context is
if I do:
em.persist(person);
em.flush();
em.clear();
for (Job j : (List<Job>) em.createQuery("from Job").getResultsList()) {
System.out.println("my order is " + j.getOrder());
}
Without the em.clear(), all the orders in that previous code snippet are NULL. So within
the current persistence context, the updates to the order property are not making it to
the Job object. Perhaps this is by design. Either way, this is just lovely documentation
to share with others who are betting their heads against the wall.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:49 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Dan Allen commented on ANN-632:
-------------------------------
Oh, and by the way. The name "order" for the column in the example was a most
unfortunate one because it is a reserved SQL word. Let's assume that I had used the
column name "idx" or "serial_number".
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [Hibernate-JIRA] Resolved: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Christian Bauer resolved ANN-632.
---------------------------------
Resolution: Rejected
There are thousands of people who have no issue following the examples in section
2.4.6.2.3. Bidirectional association with indexed collections:
@Entity
public class Parent {
@OneToMany
@org.hibernate.annotations.MapKey(columns=@Column(name="name"))
@JoinColumn(name="parent_id", nullable=false)
private Map<String, Child> children;
...
}
@Entity
public class Parent {
...
@ManyToOne
@JoinColumn(name="parent_id", insertable=false, updatable=false,
nullable=false)
private Parent parent;
...
}
Your mapping is not the same. I personally have several bidirectional one-to-many lists
working just fine. There are test cases. Use the user forum if you need help.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:59 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Christian Bauer commented on ANN-632:
-------------------------------------
Of course you need to replace @MapKey in the documentation example with @IndexColumn.
Other than that, the same applies for lists as it does for maps.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:05 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Dan Allen commented on ANN-632:
-------------------------------
I mean come on, is space so scarce that you cannot include both examples. They are clearly
not the same. Yeah, sure, you can make the leap, but imagine someone just starting out
who is not so familiar with Hibernate. Just add the example for @IndexColumn to supplement
the @MapKey in respect of people's time. There are also thousands of people that spend
a day or more trying to make that leap.
Also, it still doesn't answer the question as to why the child entity doesn't get
updated.
Oh, and by the way. Clearly there is a mistake in that documentation because the Parent
entity is displayed twice. The Child entity is missing. That makes it even MORE confusing.
Yes, I am being stubborn, but I feel that I have a case.
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 p.m.
New subject: [Hibernate-JIRA] Updated: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Emmanuel Bernard updated ANN-632:
---------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
@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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 p.m.
New subject: [Hibernate-JIRA] Reopened: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Emmanuel Bernard reopened ANN-632:
----------------------------------
Assignee: Diego Pires Plentz
Hi Diego,
if you have time, can you have a look at this doc issue?
@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: Bug
Components: documentation
Affects Versions: 3.3.0.ga
Reporter: Dan Allen
Assignee: Diego Pires Plentz
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Diego Pires Plentz commented on ANN-632:
----------------------------------------
Sure.
@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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:17 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Diego Pires Plentz commented on ANN-632:
----------------------------------------
Just an update. The "Parent" dup class problem is solved by ANN-616.
@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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Rich Eggert commented on ANN-632:
---------------------------------
I agree that the existing documentation is not at all clear as to how to do this. I ran
into when I set nullable=false and my database started throwing null value constraint
exceptions.
Let me see if I'm understanding this correctly...
In the generic case (Parent-Child example), in order to get true List behavior from the
collection, my code needs to look something like this:
@Entity
class Parent
{
@OneToMany
@org.hibernate.annotations.IndexColumn(name="child_index", nullable=false,
base=0)
@JoinColumn(name="parent_id", nullable=false)
private List<Child> children;
...
}
@Entity
class Child
{
@ManyToOne(optional=false)
@JoinColumn(name="parent_id", insertable=false, updatable=false,
nullable=false)
private Parent parent;
...
}
Does this look correct?
By the way, I beat you to the Parent-Parent typo. ;-)
@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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
J commented on ANN-632:
-----------------------
I also had some simular problems. I thought it was a bug, but it wasn't. When using
IndexColumn you carefully have to know:
-where you define the inverse side
-that you shouldn't use the inverse side for saving the index
-that you save in the correct order of parent and child.
-how to swap from inverse side if needed.
Dan Allen, in your first example you have: mappedBy = "job". I think this should
be mappedBy = "person', because the mappedBy attribute has to be the inverse
property of the target entity.
Second, in your usage of the first example, you use: person.getJobs().add(job1); But this
is on the inverse side, so it should be job1.setPerson(person) instead. (Or you should
make a convenience method, of you should change the inverse side.)
Also took me a lot of time before I found my problem.
Btw I enjoy reading your new Seam book :-)
@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 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:06 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Al Le commented on ANN-632:
---------------------------
This is all fine and documented for bidirectional associations. But what if I have an
unidirectional one with JoinColumn? The index column doesn't get set. I know this is
not recommended but we'd still like to use it.
Example:
class Parent {
@OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER)
@JoinColumn(name = "parent_id")
@IndexColumn(name = "child_index", nullable = false)
private List<Child> children = new ArrayList<Child>();
// Getters and Setters omitted
}
class Child {
// Some attributes not related to the association. There is no java field for the
child_index.
// But the DB table has this column (which does not allow NULL values).
}
In the code, I do something like this:
Parent parent = new Parent();
parent.getChildren().add(new Child("aChild"));
entityManager.save(parent);
In the generated SQL (for child insertion), the column 'child_index' does not even
occur. As a result, I have a DB constraint violation.
What am I doing wrong? Or is this really an issue in Hibernate?
@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 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Al Le commented on ANN-632:
---------------------------
I found a solution (or, rather, a workaround). I made the column 'child_index' in
the DB nullable. Now the index is correctly set.
The reason why it works now is that when the association is managed by the 'one'
side, the insert is done in two stages. First, an INSERT is done for each child element,
and then an UPDATE is executed that sets the child_index. This two-stage procedure
doesn't work if the index column does not allow NULL values.
From the DB model perspective, it would be desirable that the column
does _not_ allow NULL value.
One way to achieve this (IIUC) would be to make the 'many' side manage the
association. But then I'd have to manually set the value of the index column.
Ideally, the two things (automatic setting of the index column and having it as NOT NULL
in the DB) would be possible at the same time.
@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 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:08 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-632) @IndexColumn doesn't set value of index column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-632?page=co...
]
Jens X Augustsson commented on ANN-632:
---------------------------------------
On the original issue I totally agree with Allen - just adding Bauer's "Of
course...." comment together with some wording like "...true indexed
lists..." could save us (me) many hours - especially since googling it up or simply
search in the reference would be more effective.
@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 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5632
days inactive
6197
days old
hibernate-issues@lists.jboss.org
15 comments
8 participants
participants (8)
-
Al Le (JIRA) -
Christian Bauer (JIRA)
-
Dan Allen (JIRA)
-
Diego Pires Plentz (JIRA)
-
Emmanuel Bernard (JIRA)
-
J (JIRA)
-
Jens X Augustsson (JIRA)
-
Rich Eggert (JIRA)