Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Guido L. (JIRA) <no...@at...> - 2006-07-27 10:57:28
|
@OrderBy does not work with inherited properties
------------------------------------------------
Key: ANN-401
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-401
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.cr1
Environment: Hibernate 3.2, MySql 4, Windows XP
Reporter: Guido Laures
Using an @OrderBy with an inherited property produces an SQL Exception.
Example:
@Entity
class Base {
...
public int getPropertyForOrderBy(){ return propertytoOrderBy; }
...
}
@Entity
@PrimaryKeyJoinColumn(name="a_id")
class A extends Base {
...
}
@Entity
@PrimaryKeyJoinColumn(name="b_id")
class B extends Base {
...
@OneToMany(mappedBy = "someProp", cascade = { CascadeType.ALL })
@OrderBy("propertyToOrderBy")
public Set<A> getASet() {
return this.aSet;
}
...
}
Thus, if A references a set of Bs and wants it to be ordered by a property of B's base class Base it crashes. The generated SQL string tries to find the property from the base class in the table of the inerited class (A) which fails.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Matt S. (JIRA) <no...@at...> - 2006-07-27 02:54:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951?page=comments#action_23784 ] Matt Solnit commented on HHH-1951: ---------------------------------- P.S. Using version 10gR2 of the Oracle JDBC driver. > Table using back-tick not passing validation on Oracle > ------------------------------------------------------ > > Key: HHH-1951 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1951 > Project: Hibernate3 > Type: Bug > Versions: 3.1.3 > Environment: Client: Hibernate 3.1.3, Java 1.5.0_06, Mac OS X 10.4.7 > Database server: Windows XP SP2, Oracle XE > Reporter: Matt Solnit > > > I have a table mapping that looks similar to the following: > <class name="User" table="`User`"> > <!-- etc. --> > Notice the back-ticks around the table name. > When I use Hibernate to create the schema for me, it correctly generates a table name called "User" (including the quote marks). But when I validate the schema, it cannot find the table and so validation fails. > I am thinking the problem is somewhere in org/hibernate/tool/hbm2ddl/DatabaseMetadata.getTableMetadata(). It tries to look for "USER", because OracleDatabaseMetaData.storesUpperCaseIdentifiers() returns true. But the code doesn't realize that quoted tables are a special case and it has to look for "User" instead. > Another symptom of the same problem is that if I generate a schema update script, it will attempt to re-create the existing table. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-26 21:20:48
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-712?page=all ] Max Rydahl Andersen closed HBX-712: ----------------------------------- Fix Version: 3.2beta7 Resolution: Fixed fixed > Bad link on http://www.hibernate.org/255.html > --------------------------------------------- > > Key: HBX-712 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-712 > Project: Hibernate Tools > Type: Bug > Reporter: Dennis C. Byrne > Priority: Trivial > Fix For: 3.2beta7 > > > Click on "documentation and screenshots " at http://www.hibernate.org/255.html . > Browser goes to http://www.hibernate.org/5.html#A13 , should be http://www.hibernate.org/5.html#A10 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 21:14:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1947?page=all ] Steve Ebersole closed HHH-1947: ------------------------------- Resolution: Fixed fixed in head and 3.2 branch > OF part of MEMBER OF is optional > --------------------------------- > > Key: HHH-1947 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1947 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > entity_expression [NOT] MEMBER [OF] collection_valued_path_expression -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 20:40:40
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948?page=all ] Steve Ebersole reassigned HHH-1948: ----------------------------------- Assign To: Steve Ebersole > Query Idetification variables are case insensitive in JPA > --------------------------------------------------------- > > Key: HHH-1948 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > see EJBQLTest.testIdentifierCaseSensitive() > select object(H) from Human h should not fail -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Nick P. (JIRA) <no...@at...> - 2006-07-26 20:35:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=comments#action_23785 ] Nick Palombo commented on HHH-1615: ----------------------------------- Ran into this today with Microsoft SQL Server. > GROUP BY entity does not work > ----------------------------- > > Key: HHH-1615 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615 > Project: Hibernate3 > Type: Bug > Components: query-hql > Versions: 3.1.3 > Environment: PostgreSQL 8.1.3, Hibernate 3.1.3 > Reporter: Xavier Bugaud > > > The query : "select cat, count(*) from Cat cat group by cat" does not work. > ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function > See : > - http://forum.hibernate.org/viewtopic.php?t=953716 > - http://jira.nhibernate.org/browse/NH-528 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 19:07:56
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948?page=all ] Steve Ebersole resolved HHH-1948: --------------------------------- Resolution: Fixed applied to head and 3.2 branch; note that this requires that the JPA-QL compliance setting be enabled... > Query Idetification variables are case insensitive in JPA > --------------------------------------------------------- > > Key: HHH-1948 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > see EJBQLTest.testIdentifierCaseSensitive() > select object(H) from Human h should not fail -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-26 18:45:00
|
having trim(BOTH from c.name) translated into having ltrim(rtrim(BOTH)) on DB2
------------------------------------------------------------------------------
Key: HHH-1949
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1949
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr3
Reporter: Emmanuel Bernard
Assigned to: Steve Ebersole
Priority: Blocker
Fix For: 3.2.0.ga
same for LEADING and TRAILING
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 18:32:03
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1945?page=all ] Steve Ebersole closed HHH-1945: ------------------------------- Resolution: Rejected already fixed > OrderedSetType.instantiate() should be OrderedSetType.instantiate(int) to override SetType.instantiate(int) > ----------------------------------------------------------------------------------------------------------- > > Key: HHH-1945 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1945 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Environment: 3.2.0 CR3 > Reporter: Gordon Cosgrave > > > A many-to-many PersistentSet with an order-by specified is backed by a HashSet in H3.2.0rc3, it was correctly a LinkedHashSet in H3.0.5. > This is because OrderedSetType.instantiate() should be OrderedSetType.instantiate(int) to override SetType.instantiate(int). > The same applies to OrderedMapType. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 18:21:01
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948?page=comments#action_23775 ] Steve Ebersole commented on HHH-1948: ------------------------------------- sigh... > Query Idetification variables are case insensitive in JPA > --------------------------------------------------------- > > Key: HHH-1948 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > see EJBQLTest.testIdentifierCaseSensitive() > select object(H) from Human h should not fail -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 17:21:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1713?page=all ] Steve Ebersole resolved HHH-1713: --------------------------------- Fix Version: 3.2.0.ga Resolution: Fixed Assign To: Steve Ebersole applied on head and 3.2 branch > AbstractEntityPersister causes an exception when a row in a joined table is missing with fetch="select" > ------------------------------------------------------------------------------------------------------- > > Key: HHH-1713 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1713 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1 > Environment: Hibernate 3.1.3, 3.2.0cr1 > Oracle 9i (using odjbc14.jar from Oracle 10.1.0.4) > Reporter: Mike Dillon > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0.ga > Attachments: AbstractEntityPersister.java.patch, AbstractEntityPersister.java.patch, BasicEntityPersister.patch > > > When using the <join> mapping, the behavior of AbstractEntityPersister when the joined row is missing is not consistent between fetch="join" and fetch="select". > When fetch="join" and the row is missing, the AbstractEntityPersister simply sets all the outer joined fields to null since that's what comes back from the database. However, when fetch="select" and the row is missing, an SQLException is thrown. The reason is that the call to ResultSet.next() is not checked to see if a row is available before calling ResultSet.getXXXX(). In our Oracle enviroment, this resulted in a cryptic JDBC error about an "Exhausted Resultset". > The fix is to check the return value of ResultSet.next(). I have attached a patch with a proposed fix for this issue. To be consistent with the current behavior of fetch="join", it explicitly sets all fields that come from the "sequential select" to null when the select does not produce any rows. This contradicts the hibernate-mapping DTD which says that the "optional" attribute on <join> defaults to false, but since that attribute is undocumented and the current implementation doesn't seem to respect this attribute even when fetch="join", I decided to be consistent with the actual semantics of fetch="join". > The behavior of the optional attibute probably needs to be fixed in both cases, but I didn't address that with my patch. It seems that optional only works as advertised when Hibernate is able to produce a query with a single polymorphic join and can use an inner join instead of a left outer join. > My patch was created against Hibernate 3.1.3, but I looked at the same code in 3.2.0cr1 and it has not changed. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Francois J. (JIRA) <no...@at...> - 2006-07-26 16:04:21
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938?pa= ge=3Dcomments#action_23776 ]=20 Francois Jean commented on HHH-1938: ------------------------------------ Hello, I would like to know if there is a "workaround" for this problem (describe = at: http://jira.jboss.com/jira/browse/HIBERNATE-37). We did not have the pr= oblem when using JBoss 4.0.4RC2 but got it when moving to JBoss 4.0.4GA. We= naively tried to replace "hibernate3.jar" and "javasssit.jar" on the JBoss= 4.0.4GA with those from RC2 but it did not fixed the problem. Which files = need to be replaced in JBoss 4.0.4GA to "workaround" that problem? Or does a patch already been made in the source repository? Thank You, Fran=C3=A7ois J. > Proxy creation may fails when duplicate methods are used by the compiler > ------------------------------------------------------------------------ > > Key: HHH-1938 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1938 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Minor > > > http://jira.jboss.com/jira/browse/JASSIST-24 --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-26 15:22:29
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1947?page=all ] Steve Ebersole reassigned HHH-1947: ----------------------------------- Assign To: Steve Ebersole > OF part of MEMBER OF is optional > --------------------------------- > > Key: HHH-1947 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1947 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > entity_expression [NOT] MEMBER [OF] collection_valued_path_expression -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Gordon C. (JIRA) <no...@at...> - 2006-07-26 14:23:18
|
OrderedSetType.instantiate() should be OrderedSetType.instantiate(int) to override SetType.instantiate(int)
-----------------------------------------------------------------------------------------------------------
Key: HHH-1945
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1945
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr3
Environment: 3.2.0 CR3
Reporter: Gordon Cosgrave
A many-to-many PersistentSet with an order-by specified is backed by a HashSet in H3.2.0rc3, it was correctly a LinkedHashSet in H3.0.5.
This is because OrderedSetType.instantiate() should be OrderedSetType.instantiate(int) to override SetType.instantiate(int).
The same applies to OrderedMapType.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-26 13:36:22
|
Query Idetification variables are case insensitive in JPA
---------------------------------------------------------
Key: HHH-1948
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1948
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr3
Reporter: Emmanuel Bernard
Priority: Blocker
Fix For: 3.2.0.ga
see EJBQLTest.testIdentifierCaseSensitive()
select object(H) from Human h should not fail
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-26 13:19:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941?page=all ] Max Rydahl Andersen closed HHH-1941: ------------------------------------ Resolution: Fixed in both 3.2 and HEAD now > Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it > ------------------------------------------------------------------------------------------------- > > Key: HHH-1941 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.cr3 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 3.2.0.ga > > > We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools. > I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/wrong. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-26 12:36:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-711?page=all ] Max Rydahl Andersen updated HBX-711: ------------------------------------ Priority: Minor (was: Major) Workaround: -Dfile.encoding=whatyouwant > Support of several charset in import.sql file > --------------------------------------------- > > Key: HBX-711 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-711 > Project: Hibernate Tools > Type: Improvement > Environment: Hibernate 3.2, all database platforms > Reporter: Thomas SEGISMONT > Priority: Minor > > Original Estimate: 1 day > Remaining: 1 day > > For the moment, only the default execution platform charset encoding is supported for the import.sql file. Indeed, in the org.hibernate.tool.hbm2ddl.SchemaExport class, the reader of that file is created like this : > importFileReader = new InputStreamReader( stream ); > In my development team, we have windows, linux and mac os and we want to use UTF-8 (we need special chars like the euro sign). > It would be helplful to have a way to tell Hibernate what charset encoding it should use. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Adrien (JIRA) <no...@at...> - 2006-07-26 10:12:09
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HB-534?page=comments#action_23768 ] Adrien commented on HB-534: --------------------------- Gavin set this issue as Duplicate, but without saying the duplicate issue. As far as I know, this issue is still not corrected in version 3.1.3. The patch is still not apply. I just got the problem again recently, looking in the tracker for existing issue, and found my own issue submmited two years ago. I am not sure I should submit this again and again. If you feel like it, go ahead. Adrien > Table schema use in DatabaseMetadata > ------------------------------------ > > Key: HB-534 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-534 > Project: Hibernate2 > Type: Bug > Components: core > Versions: 2.1 beta 4 > Environment: Hibernate 2.1 beta 4, Oracle 8i > Reporter: Adrien > Attachments: DatabaseMetadata.java, HB-534_patch.txt, TableMetadata.java > > > When using SchemaUpdate, the DatabaseMetaData.getTableMetadata() looks for a table with the correct table name in any database schema and it take the first one it found. This behavior is uncorrect if I have a table existing in different schemas. > The correct behavior would be to first look in the schema with the login name and after in any schema. > user1.article > user2.article > I connected whith user2, DatabaseMetaData should first look for user2.article, then if not found to %.article. > Adrien -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-25 22:05:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1943?page=all ] Emmanuel Bernard resolved HHH-1943: ----------------------------------- Resolution: Fixed > PersistenceContext not checked to see whether the associated entity is transient or not > --------------------------------------------------------------------------------------- > > Key: HHH-1943 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1943 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: 3.2.0.ga > > > This affects HEM -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Scott M. (JIRA) <no...@at...> - 2006-07-25 18:18:23
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931?page=comments#action_23762 ] Scott Marlow commented on HHH-1931: ----------------------------------- javassist assumes that pojo class Silly isn't instrumented, which is correct. Javassist instrumentation for Container class contains: public void doSillyThing(Silly silly) { silly.value = "true"; } cglib seems to assume that pojo class Silly is instrumented, which is not correct. cqlib instrumentation for Container class contains: public void doSillyThing(Silly silly) { silly.$cglib_write_value("true"); } Silly class looks like: package test; public class Silly { public Silly() { } public String value; } > verify that the instrument tasks actually work > ---------------------------------------------- > > Key: HHH-1931 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931 > Project: Hibernate3 > Type: Task > Components: core > Reporter: Steve Ebersole > Assignee: Scott Marlow > Attachments: InstrumentBugTest.zip > > > It appears they may not in all cases. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-07-25 16:48:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1939?page=comments#action_23761 ] Steve Ebersole commented on HHH-1939: ------------------------------------- Here is a good place to start: http://fisheye.jboss.com/viewrep/Hibernate/trunk/Hibernate3/src/org/hibernate/persister/entity Have a look at: 1) AbstractEntityPersister 2) JoinedSubclassEntityPersister 3) SingleTableEntityPersister > Extended support for mixing table-per-subclass and table-per-hierarchy > ---------------------------------------------------------------------- > > Key: HHH-1939 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1939 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.1.3 > Environment: Hibernate 3.1.3, Postgresql 8.1 > Reporter: Jason Bennett > > > http://forum.hibernate.org/viewtopic.php?t=962067 > At present, Hibernate allows limited mixing of table-per-hierarchy and table-per-subclass. Specifically, once a particular inheritance branch begins using TPS, it cannot switch back to TPH. > In our domain (as described in the above forum post), we have several fine-grained objects near the top of our hierarchy, with some bulkier objects lower down. What we would like to do is to run TPS for the higher, smaller classes (where we have referential integrity reasons to break them out), and then switch back to table-per-hierarchy further down, where the majority of our queries are run. > I would be happy to assist in implementation, given some direction. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: George G. (JIRA) <no...@at...> - 2006-07-25 16:30:14
|
Interfaces PreInsertEventListener and PreUpdateEventListener are badly javadoc-documented
-----------------------------------------------------------------------------------------
Key: HHH-1942
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1942
Project: Hibernate3
Type: Task
Components: documentation
Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3
Reporter: George Gastaldi
Priority: Trivial
Provide proper documentation for org.hibernate.event.PreUpdateEventListener and org.hibernate.event.PreInsertEventListener.
Like:
1) What does the return method (boolean) of their methods mean ?
2) Who calls it and when ?
George.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Thomas S. (JIRA) <no...@at...> - 2006-07-25 15:36:13
|
Support of several charset in import.sql file
---------------------------------------------
Key: HBX-711
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-711
Project: Hibernate Tools
Type: Improvement
Environment: Hibernate 3.2, all database platforms
Reporter: Thomas SEGISMONT
For the moment, only the default execution platform charset encoding is supported for the import.sql file. Indeed, in the org.hibernate.tool.hbm2ddl.SchemaExport class, the reader of that file is created like this :
importFileReader = new InputStreamReader( stream );
In my development team, we have windows, linux and mac os and we want to use UTF-8 (we need special chars like the euro sign).
It would be helplful to have a way to tell Hibernate what charset encoding it should use.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Scott M. (JIRA) <no...@at...> - 2006-07-25 15:10:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931?page=comments#action_23760 ] Scott Marlow commented on HHH-1931: ----------------------------------- Doing the following steps with cglib, results in the following error: 1. ant 2. ant instrument 3. ant run . . . [java] 09:39:38,527 INFO SchemaExport:196 - schema export complete [java] Hibernate: select max(ID) from CONTAINER [java] Exception in thread "main" java.lang.NoSuchMethodError: test.Silly.$cglib_write_value(Ljava/lang/String;)V [java] at test.Container.doSillyThing(Container.java:19) [java] at Test.testCreate(Test.java:31) [java] at Test.main(Test.java:18) [java] Java Result: 1 > verify that the instrument tasks actually work > ---------------------------------------------- > > Key: HHH-1931 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931 > Project: Hibernate3 > Type: Task > Components: core > Reporter: Steve Ebersole > Assignee: Scott Marlow > Attachments: InstrumentBugTest.zip > > > It appears they may not in all cases. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 14:27:12
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941?page=comments#action_23759 ] Max Rydahl Andersen commented on HHH-1941: ------------------------------------------ committed to HEAD for now. > Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it > ------------------------------------------------------------------------------------------------- > > Key: HHH-1941 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.cr3 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 3.2.0.ga > > > We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools. > I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/wrong. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
93 messages has been excluded from this view by a project administrator.
