September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-5557) Sybase supports alias length upto 30 characters

by Strong Liu (JIRA)

Sybase supports alias length upto 30 characters ----------------------------------------------- Key: HHH-5557 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5557 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.6.0.CR1 Sybase supports alias length upto 30 characters (more than 10 as it is indicated) -- 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

13 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5555) Incorrected examples shown in Hibernate Annotation documentation

by Zemian Deng (JIRA)

Incorrected examples shown in Hibernate Annotation documentation ---------------------------------------------------------------- Key: HHH-5555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5555 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.5.5 Reporter: Zemian Deng I am reporting two issues with Hibernate Annotation documentation: 1) The example shown in section "2.2.3.2.3. @IdClass" doesn't use @IdClass. 2) The example shown in section "2.2.3.2.2. Multiple @Id properties" is confusing. It says "... does not require an extra embeddable component.", but yet the example shown a @Embeddable. -- 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

13 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5547) Remove "old" docbook sources and cleanup all HEAD references to simhei.ttf

by Steve Ebersole (JIRA)

Remove "old" docbook sources and cleanup all HEAD references to simhei.ttf -------------------------------------------------------------------------- Key: HHH-5547 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5547 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.6, 3.6.0.CR1 Removing the documentation/manual/old path is what relates to 3.5.6 and 3.6.0.CR1. Cleaning up references to simhei.ttf will occur across all projects/branches -- 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

13 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5553) DbTimestamp uses local time for @Version field on Oracle 11g

by Chris Pheby (JIRA)

DbTimestamp uses local time for @Version field on Oracle 11g ------------------------------------------------------------ Key: HHH-5553 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5553 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2 Environment: Oracle 10g2 Reporter: Chris Pheby Attachments: dbtimestamp.patch When you using DbTimestamp to use the database to seed the timestamp (for the @Version oplock field), this delegates to getCurrentTimestampSelectString(). On Oracle 10g this invokes "select systimestamp from dual". This returns the server's local time. This causes problems when crossing the cutoff between (for example) British Summer Time and UTC. The standard SQL function, current_timestamp (returned by getCurrentTimestampSQLFunctionName should be used instead. This always returns UTC time. public String getCurrentTimestampSelectString() { return "select systimestamp from dual"; // suggest changing to // return "select " + getCurrentTimestampSQLFunctionName() + " from dual"; } public String getCurrentTimestampSQLFunctionName() { // the standard SQL function name is current_timestamp... return "current_timestamp"; } NB getCurrentTimestampSelectString() is only referenced from the DbTimestamp 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

13 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5446) Create a n envers tutorial guide

by Steve Ebersole (JIRA)

Create a n envers tutorial guide -------------------------------- Key: HHH-5446 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5446 Project: Hibernate Core Issue Type: Sub-task Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 Create a tutorial guide that demonstrates using envers. I guess this should build on the annotations tutorial. -- 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

13 years, 7 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HV-364) @Email does not fail if tilda (~) or forward slash (/) are in the domain

by Anthony Gerrard (JIRA)

@Email does not fail if tilda (~) or forward slash (/) are in the domain ------------------------------------------------------------------------ Key: HV-364 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-364 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.Final Environment: 4.1.0 Reporter: Anthony Gerrard Assignee: Hardy Ferentschik The following email addresses do not result in constraint validations. I believe they should test(a)~mydomain.com test@mydomain/com Looking at the mail specification it does seem to allow these email addresses but they're not compatible with javax.mail.internet.InternetAddress or indeed most email servers. -- 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

13 years, 7 months

2
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-1100) Invalidate cache on StaleObjectStateException

by Nico De Groote (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1100?page=c... ] Nico De Groote commented on HHH-1100: ------------------------------------- What is the state for this issue? This isn't fixed in the 3.5.5 version. > Invalidate cache on StaleObjectStateException > ---------------------------------------------- > > Key: HHH-1100 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1100 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Gavin King > Assignee: Gavin King > Priority: Critical > > We should probably invalidate the second-level cache when a StaleObjectStateException occurs. Need to think this through. -- 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

13 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3789) Allow for pluggable stats collection

by Patrick Moore (JIRA)

Allow for pluggable stats collection ------------------------------------ Key: HHH-3789 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3789 Project: Hibernate Core Issue Type: Patch Affects Versions: 3.5 Reporter: Patrick Moore Attachments: patch.txt I have a need to do more fine-grain stats collection. The current implementation does not allow for a replacement stats collection. This patch allows for the default stats code to be replaced with a custom implementation. -- 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

13 years, 8 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5549) Add option for use of weak references in the session cache

by Archie Cobbs (JIRA)

Add option for use of weak references in the session cache ---------------------------------------------------------- Key: HHH-5549 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5549 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.2 Reporter: Archie Cobbs Hibernate's session cache requires manual action (i.e., evict() and/or clear()) to prevent it from growing without bound when iterating over a large set of entities. This was surprising to me the first time I encountered it, because most people's concept of a "cache" includes the idea of transparency, i.e., the cache is not apparent except in increased performance. Hibernate's cache, even within a read-only transaction, effectively has a built-in memory leak. But anyway, this problem can be fixed easily. Suggest adding a new feature which would (optionally) allow the session cache to be configured to automatically evict unmodified objects that were no longer referenced. The session cache would change to use two kinds of references to objects in the cache: normal strong references for objects that are new or modified in any way, and weak references for objects that have not been modified. Hibernate would have to switch a weakly referenced object into a strongly referenced one once it was modified. This way, unmodified, weakly referenced objects would automatically fall out of the cache when they were no longer referenced by the application, and the "iterate over a large dataset" memory leak would be fixed. -- 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

13 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5541) Change from class to interface leads to IncompatibleClassChangeError (org.hibernate.stat.EntityStatistics and co.)

by Cédrik LIME (JIRA)

Change from class to interface leads to IncompatibleClassChangeError (org.hibernate.stat.EntityStatistics and co.) ------------------------------------------------------------------------------------------------------------------ Key: HHH-5541 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5541 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final Reporter: Cédrik LIME Hibernate 3.5.0 introduced a concurrent implementation for Statistics. Thus the classes of {{org.hibernate.stat.*}} became interfaces and lo and behold! a Java 5 concurrent implementation was born, and all rejoiced at this marvel. But in the land of compiled binaries, some said that a {{java.lang.IncompatibleClassChangeError}} would rear its ugly head since where a Class was expected an Interface would appear, and so the current thread would stop its processing with an Error. And it was said in the kingdom of Hibernate that documentation was forthcoming that everyone should re-compile their dependant 3rd-party libraries, whether one could access the 3rd-party sources or not. In an ironic twist, now that Hibernate 3.6 depends on Java 5, we still have the non-concurrent implementation lying around unused... All prose apart, this bug means I can not distribute a {{.jar}} that is compiled against Hibernate 3.1 and that works for all released Hibernate versions. I don't want impose my users the hassle to re-compile (even if I provide the source code), but I guess this 3.5.0 change leaves me no choice... This should at least be clearly documented. -- 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

13 years, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2010