[Hibernate-JIRA] Created: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
12:57 a.m.
Allow enhanced.TableGenerator to segment itself per entity as default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.3.x
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a base
entity class.
--
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:15 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Steve Ebersole updated HHH-3454:
--------------------------------
Fix Version/s: 3.4
3.2.x
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.x, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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:23 a.m.
New subject: [Hibernate-JIRA] Resolved: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Steve Ebersole resolved HHH-3454.
---------------------------------
Resolution: Fixed
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.x, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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:51 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Steve Ebersole commented on HHH-3454:
-------------------------------------
The setting to control this is 'prefer_entity_table_as_segment_value'
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.x, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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
2:54 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Drew Kutcharian commented on HHH-3454:
--------------------------------------
I don't think prefer_entity_table_as_segment_value works with Hibernate Annotations.
In my entity I have:
@Id
@GenericGenerator(name = "idGenerator", strategy =
"org.hibernate.id.enhanced.TableGenerator", parameters = {
@Parameter(name = "optimizer", value = "pooled"), @Parameter(name =
"initial_value", value = "1"),
@Parameter(name = "increment_size", value = "10"), @Parameter(name =
"prefer_entity_table_as_segment_value", value = "true") })
@GeneratedValue(generator = "idGenerator")
@Column(name = "id")
private Integer id = null;
But in the hibernate_sequences table, there's only one row with name
"default" and all the entities use the next_val of that.
Please advise if you want a JIRA separate issue for this.
Thanks,
Drew
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.1, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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
11:29 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Drew Kutcharian commented on HHH-3454:
--------------------------------------
BTW, I'm using Hibernate 3.3.1.GA with Hibernate Annotations 3.4.0.GA
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.1, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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
8:40 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Steve Ebersole commented on HHH-3454:
-------------------------------------
I have tests showing this works w/o annotations, and just looked at the code for how
annotations deals with this and I do not see any problems with it. Please make *sure* you
are using the Hibernate Core version you think you are using
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.1, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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
11:11 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3454) Allow enhanced.TableGenerator to segment itself per entity as default
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454?page=c...
]
Drew Kutcharian commented on HHH-3454:
--------------------------------------
Steve,
I'm sure Hibernate versions are correct since:
1) I use Ivy to download the correct versions of libraries from JBoss Maven repository
2) As a workaround I created my own custom id generator that extends TableGenerator
(com.foo.bar.IDGenerator) and all it does is it overrides the configure method as:
@Override
public void configure(final Type type, final Properties params, final Dialect
dialect) throws MappingException {
params.put("optimizer", "pooled");
params.put("initial_value", "1");
params.put("increment_size", "10");
params.put("prefer_entity_table_as_segment_value",
"true");
super.configure(type, params, dialect);
}
and in my entity I have:
@Id
@GenericGenerator(name = "idGenerator", strategy =
"com.foo.bar.IDGenerator")
@GeneratedValue(generator = "idGenerator")
@Column(name = "id")
private Integer id =
null;
and things work per spec.
I was worried I wasn't using the annotations correctly that's why I commented to
this JIRA in the first place.
This is really strange.
cheers,
Drew
Allow enhanced.TableGenerator to segment itself per entity as
default
---------------------------------------------------------------------
Key: HHH-3454
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3454
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.1, 3.4
Currently TableGenerator use a static string ("default" ) for its default
segment column name. The implication is that all TableGenerators defined without
specifying a segment value explicitly ended up using the same row.
Where this cam up was in the case of annotations where the generator is attached to a
base entity class.
--
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
5892
days inactive
5969
days old
hibernate-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Drew Kutcharian (JIRA) -
Steve Ebersole (JIRA)