|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Comment for the post 23/Aug/12 1:24 PM
The intersection table was created there because I have @AuditJoinTable(name="search_param_auidit") in the search class
@AuditJoinTable(name="search_param_auidit")
@Fetch(FetchMode.SUBSELECT)
@OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL)
@JoinColumn(name = "SEARCH_ID")
public Set<SearchParameter> getSearchParams() { return searchParams; }
I commented the @AuditJoinTable line and ran the test again, then I can see the hibernate is trying to insert into a different table and it look like an intersection table, please see below the line from the log.
Hibernate: insert into customer.Search_SearchParameter_AUD (REVTYPE, REV, SEARCH_ID, id) values (?, ?, ?, ?)
The Search_param_test_audit table is still inserting the search_id null.
the first point is why the hibernate is trying to insert values to an intersection table which I don't mention anywhere.