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: <leg...@at...> - 2003-12-11 06:43:18
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:42 AM
This is a dupe of HB-147. (This is a VERY popular feature request.)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-294
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-294
Summary: Precompilation of Hibernate mappings (e.g. serialized Configuration/SessionFactory)
Type: New Feature
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
toolset
Versions:
2.1 beta 2
Assignee:
Reporter: Aksel Hilde
Created: Wed, 27 Aug 2003 9:26 AM
Updated: Thu, 11 Dec 2003 12:42 AM
Environment: -
Description:
To use Hibernate at run-time one must first load and "compile" all the mapping files. Something like this:
Configuration config = ...; //Load all properties and mapping files
SessionFactory sessionFactory = config.buildSessionFactory();
This is very nice when the domain model change rapidly, because things are always up to date when unit testing. But when the domain model is relatively stable, this "compilation" takes quite some time.
It would therefore be very nice to have a tool to "pre-compile" all the mappings and store them in a file in serialized form, and the ability to create a SessionFactory or at least a Configuration at run-time by loading the pre-compiled mappings.
This would speed up unit testing a lot for us!! We have a J2SE-client + J2EE-server app, but are doing all our business logic unit testing in a single VM. So when I would like to run a jUnit test, then the time taken to compile mappings is relatively high compared to the time the actual test takes. And now we only have about 20 entities, pretty soon that number will double or tripple.
Anyway, thanks for a great O/R tool!!
Best regards
Aksel Hilde
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:41:16
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@hi...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-417 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-417 Summary: support createCriteria() for <key-many-to-one> Type: New Feature Status: Open Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Gavin King Reporter: Sebastien Cesbron Created: Wed, 22 Oct 2003 3:07 AM Updated: Thu, 11 Dec 2003 12:40 AM Environment: Win2k SQLServer with jTds driver Description: I have one class Bar with a primary key composed of a 'key-many-to-one' to a class Foo. I want to find a Bar instance with a Foo id so I have this criteria : Criteria criteria = session.createCriteria(Bar.class); criteria.createCriteria("foo").add(Expression.eq("id", new Integer(1))); Bar bar = (Bar) criteria.uniqueResult(); Then I have this sql statement select this.ID_FOO as ID_FOO0_, this.text as text0_ from BAR this where x0_.id=1 which fails because x0_ isn't defined. With an HQL query it works. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-12-11 06:39:17
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-373 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-373 Summary: problem in the ReflectHelper leads to "could not find getter" Type: Improvement Status: Closed Priority: Minor Resolution: WON'T FIX Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Gavin King Reporter: Sherban Popescu Created: Wed, 1 Oct 2003 6:05 AM Updated: Thu, 11 Dec 2003 12:39 AM Environment: Win 2000 Description: If one has a variable like: aEndTerminal The getter/setter are generated corectly by the code generator, BUT: Because the getter/setter changes aEndTerminal to AEndTerminal, we got into this later on: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for aEndTerminal in class com.im.Trail at net.sf.hibernate.util.ReflectHelper.getGetter(ReflectHelper.java:206) at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:571) at net.sf.hibernate.persister.EntityPersister.<init>(EntityPersister.java:665) at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:29) at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:207) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627) at com.im.Main.initHibernate(Main.java:42) at com.im.Main.go(Main.java:48) at com.im.Main.main(Main.java:35) Exception in thread "main The problem is Introspector.decapitalize() It has a "special case" that we're hitting, quote from javadoc: " This normally means converting the first character from upper case to lower case, but in the (unusual) special case when there is more than one character and both the first and second characters are upper case, we leave it alone." I've created a copy of Introspector.decapitalize inside ReflectHelper.java without the "special case" , replaced all calls to Introspector.decapitalize with my new 'decapitalize' and all works like a charm. So in my opinion Introspector.decapitalize should not be used in the RelectHelper !!! This kind of bug surfaces when the variable begins with one single lower case character followed by an upper case character !! Thanks, --sherban --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-12-11 06:39:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:38 AM
You can now use access="direct" for this.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-312
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-312
Summary: Subclasses using super method not found properly
Type: Improvement
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee: Gavin King
Reporter: Jonas Van Poucke
Created: Fri, 5 Sep 2003 4:33 AM
Updated: Thu, 11 Dec 2003 12:38 AM
Description:
Whe have two classes:
--- Base Class ---
public class SuperWithMap {
private Map members;
public void setMembers(Map value) {
this.members = value;
}
public Map getMembers() {
return members;
}
public void addMember(Object member) {
members.put(member, null); // value is a dummy
}
}
--- SubClass ---
public class SubWithSet extends SuperWithMap {
public void setMembers(Set value) {
Iterator iter = value.iterator();
while (iter.hasNext()) {
super.addMember(iter.next());
}
}
}
--- Mapping ---
The subclass should use the super-classes method to set the Map:
<class
name="SuperWithMap"
table="SuperTable">
<joined-subclass
name="SubWithSet"
table="SubTable">
<key column="ref_id"/>
<map
name="members"
table="RefTable"
lazy="false"
cascade="all">
<key column="mem_id"/>
<index-many-to-many column="value_id" class="some-other-class" />
<element column="otherclassvalue" type="double"/>
</map>
</class>
Note: the reference in the map to some-other-table is ommited
--- Problem ---
When trying to load data for the subclass SubWithSet, the attribute "members" is set with the method setMembers(Set value) and not with the super-classes setMembers(Map value).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:37:18
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:37 AM
This was implemented in 2.1
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-173
Summary: Access to <meta> with the API
Type: Improvement
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Assignee: Max Rydahl Andersen
Reporter: xfgdf
Created: Thu, 10 Jul 2003 7:21 AM
Updated: Thu, 11 Dec 2003 12:37 AM
Description:
It would be great to access to the <meta> elements with the API. Something like :
String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...
May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.
Adrien
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:37:18
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 11 Dec 2003 12:36 AM
Body:
What is the status of this, Max?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-491
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-491
Summary: createSQLQuery should support joined-subclass
Type: Improvement
Status: Open
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 final
Assignee: Max Rydahl Andersen
Reporter: Max Rydahl Andersen
Created: Sat, 22 Nov 2003 1:28 PM
Updated: Thu, 11 Dec 2003 12:36 AM
Description:
select .... from persons {person}, customers {(Customer)person} where ....
where Customer is a <joined-subclass> of Person.
http://forum.hibernate.org/viewtopic.php?t=925439&highlight=createsqlquery+joined
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:37:17
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:35 AM
This has been implemented in 2.2 branch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-203
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-203
Summary: Re-use 1 class over multiple tables w/ same schema
Type: New Feature
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Sam Bravard
Created: Thu, 17 Jul 2003 3:38 AM
Updated: Thu, 11 Dec 2003 12:35 AM
Environment: All
Description:
As far as I can tell, hibernate forces you to apply a single bean against a single table. In comparison to how one normally handles larger multi-table applications in SQL, the one-class to one-table restriction is very limiting.
In many rea-world cases you tend to use multiple tables with identical column layouts (deleted but archived entires, holding queues, etc). Hibernate doesn't appear to support this methodology easily without creating numerous duplicate bean objects that only differ in their 'table' attribute in the .hbm.xml file.
It would be terrific if hibernate could support something along the lines of:
'select cat.name from eg.Cat("tablename") as cat'
so we could easily retarget the table. (the above is just an example - better syntax welcome).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:35:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:34 AM
rejecting this - it has not been asked for by anyone else and I don't like it.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-150
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-150
Summary: Add getSession method to Transaction interface
Type: New Feature
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Fix Fors:
2.1
Versions:
2.0.1
2.0.2
Assignee:
Reporter: TURIN ACCOUNT
Created: Tue, 8 Jul 2003 3:31 PM
Updated: Thu, 11 Dec 2003 12:34 AM
Description:
It should be possible to retrieve the Session associated with a Transaction from a Transaction instance. This would assist some data access implentations by exposing the relationship in a convenient and logical manner.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:33:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 11 Dec 2003 12:32 AM
Body:
1) should already be possible, right?
2) is certainly already possible: Interceptor.instantiate()
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-382
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-382
Summary: Make Hibernate Friendlier for use of Proxies and Enhanced Classes
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 final
Assignee:
Reporter: James House
Created: Mon, 6 Oct 2003 4:29 PM
Updated: Thu, 11 Dec 2003 12:32 AM
Description:
Hibernate could become friendly to applications that make use of proxies and byte-code enchanced classes in their object models.
To do so, only a couple simple new features are needed:
1) Add a construct (new method) to Configuration that lets you relate one class's mappings to another (i.e. tell Hibernate that: if you ever have to persist this class, act as if it is this other class that you already have mappings for). - This will serve to tell Hibernate that the enhanced class (who's class name is only known at run-time) should be persisted using the mappings of the original class. Note that in this case, the enhanced class only has changed behavior - no new properties.
2) Add a construct to relate a "factory" to a class's mappings, from which Hibernate should produce new instances of that class during load() operations. - This will server to tell Hibernate that it should create a new instance of a class (during load()) using the given factory, rather than using the default constructor. This way Hibernate can produce enhanced or proxied or even just sub-classes of objects without being aware of it. This feature would also be useful to other people, who simply need the object to be created a special way.
I'd be happy to donate this work if it would be accepted - just let me know (either as a comment to this issue, or via e-mail) that it will be worth my time to do the work.
james
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:28:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:27 AM
I decided a while ago to not apply this patch, since it complexifies the build process.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-69
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-69
Summary: Refactoring of Environment
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee: Gavin King
Reporter: Igor Fedorenko
Created: Sun, 11 May 2003 8:41 AM
Updated: Thu, 11 Dec 2003 12:27 AM
Description:
As discussed on Hibernate mailing list few weeks back, it would be nice to have one master definition of all Hibernate properties. This master definition can be used to produce documentation, Properties- and JavaBean- style access to Hibernate properties, JCA deployment descriptor and so on. Because all this will be derived from the same source, consistency will be guaranteed and maintenance will be significantly simplified.
This patch is the first step towards this goal. "Master" definition of Hibernate properties is defined as xml document and net.sf.hibernate.cfg.Environment has been refactored to use the master. Also, preliminary implementation of JavaBean-style access to the properties has been provided. Generation of java code is done using XSLT stylesheets.
Once this patch is accepted I will provide the following patches
I am planning to work on couple of follow-up patches (of course, if you decide to accept this patch)
- SessionFactory#openSession(Properties) for session-level properties (see for example HB-46)
- Configuration of all (relevant) Hibernate properties using JCA deployment descriptor
PS: I would appreciate if somebody (Gavin?) commented on this patch, this will help me manage my time working on follow-ups.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:26:17
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:26 AM
I applied this patch.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-515
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-515
Summary: Allow a different persister for a Subclass
Type: Patch
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 final
Versions:
2.1
Assignee: Gavin King
Reporter: Nick Johnson
Created: Tue, 2 Dec 2003 2:47 PM
Updated: Thu, 11 Dec 2003 12:26 AM
Environment: Hibernate from CVS, using the same branch we used for our custom collection persister patch (see HB-419)
Description:
In some cases it is desirable to persist a subclass differently than a class; for example, if the subclass is persisting a different number of fields or if the fields are in a different order for some reason.
This patch allows a different persister to be bound to a Subclass. If one is not defined, the parent class's persister is used (as was the case before).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:22:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:21 AM
I use MySQL + C3P0 with no problems. I think this may have been problematic in an old MySQL driver version.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-322
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-322
Summary: C3P0 autocommit property
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Craig Raw
Created: Thu, 11 Sep 2003 4:54 AM
Updated: Thu, 11 Dec 2003 12:21 AM
Description:
As discussed in the Hibernate forum, this allows the setting of a C3P0 property, c3p0.autoCommitOnClose, as described in the C3P0 javadoc for com.mchange.v2.c3p0.PoolConfig.
If this property is not set to true, C3P0 will attempt to rollback any pending transactions on connection close. One would ordinarily call commit() on the connection before closing.
In the case of mySQL however, autocommit is turned on by default, and calling commit() results in an exception. C3P0 must be instructed in this case not to rollback any pending transactions, which setting this property to true allows.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:15:17
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:13 AM
This was fixed a while ago.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-393
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-393
Summary: Send meaningful message when null passed to primitive setter(s)
Type: Patch
Status: Closed
Priority: Minor
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 11 Oct 2003 1:51 AM
Updated: Thu, 11 Dec 2003 12:13 AM
Description:
Current exception when passing null value to primitive setter does not indicate the setter that is in error. The attatched patch logs a warning message that identifies primitive value setters receiving null values.
This has been a common error among our developers and a search of the forums indicates others have hit this as well.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:08:16
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:07 AM
We won't apply this patch to the Hibernate core. It seems that AS400 users are now ok, using V5R2.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-263
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-263
Summary: Order by restriction in DB2/400 for OS/400 prior to V5R2
Type: Patch
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Assignee:
Reporter: Brian Koehler
Created: Fri, 15 Aug 2003 10:14 AM
Updated: Thu, 11 Dec 2003 12:07 AM
Environment: This patch should fix Hibernate2 for anyone attempting to use HQL to access tables on an AS/400 using V5R1 or earlier.
Description:
The primary issue is that the column name specified in the order by clause must exist in the select clause. Since Hibernate generates aliases on all selected columns, order by's never work. The patch code modifies QuerySelect to replace column selections in the order by clause with the aliases defined in the select clause. The modified QuerySelect code is only triggered if a new method defined in the Dialect class called useAliasesInOrderBy returns true. By default the Dialect method returns false, and a new subclass of the DB2Dialect called AS400DB2Dialect returns true.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:05:17
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 11 Dec 2003 12:04 AM
Body:
Hmmmmm should I apply this? Havn't decided...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-375
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-375
Summary: bag.equals and bag.hashcode implementation
Type: Patch
Status: Open
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee: Gavin King
Reporter: Emmanuel Bernard
Created: Wed, 1 Oct 2003 9:42 AM
Updated: Thu, 11 Dec 2003 12:04 AM
Description:
I implements bag.equals() and bag.hashcode() conforming the bag semantic.
I did it for hibernate 2.0.3 version (can't access head right now)
To implement it on head (1.16.2.3 right now), add the equals and hashcode version.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 06:05:17
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@hi...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-375 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-375 Summary: bag.equals and bag.hashcode implementation Type: Patch Status: Open Priority: Major Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Gavin King Reporter: Emmanuel Bernard Created: Wed, 1 Oct 2003 9:42 AM Updated: Thu, 11 Dec 2003 12:04 AM Description: I implements bag.equals() and bag.hashcode() conforming the bag semantic. I did it for hibernate 2.0.3 version (can't access head right now) To implement it on head (1.16.2.3 right now), add the equals and hashcode version. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-12-11 05:59:18
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 11:58 PM
Well, I'm not sure what you mean but you can fix the page yourself. It is a Wiki. Just clik "Edit Page".
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-538
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-538
Summary: Documentation incorrect for xDoclet jbossservice subtask
Type: Bug
Status: Closed
Priority: Minor
Resolution: INCOMPLETE
Project: Hibernate2
Versions:
2.1
Assignee:
Reporter: Roland Chan
Created: Wed, 10 Dec 2003 9:01 AM
Updated: Wed, 10 Dec 2003 11:58 PM
Environment: Hibernate 2.1, w/ xDoclet 1.2b4 and CVS Head, and Maven RC1
Description:
The document, http://www.hibernate.org/66.html, describes that with the release of 2.1 final there will be a need to add additional mbean properties to the jboss-service.xml that are not supported by hibernatedoclet. The method it uses to describe this is to create a merge file and add your elements there.
This is incorrect and misleading since the new elements will be put outside the targeted mbean which is undesired since most users will want the elements to be part of the hibernate factory mbean.
Hopefully fixing this doc will save someone else some time.
Moreover, there is support for an additional <depends> element, however, I have yet to get this to work correctly.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 05:57:25
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 11:56 PM
this is a dupe
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-543
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-543
Summary: Add method to return count(*) in Criteria
Type: New Feature
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Assignee:
Reporter: fafnirchen
Created: Wed, 10 Dec 2003 11:09 PM
Updated: Wed, 10 Dec 2003 11:56 PM
Environment: w2k
Description:
I used Criteria to query and I call method setFirstResult, setMaxResults to return some records instead of return all records. I am not only want to get these records but also want to get the total num of records fit my query condition without setFirstResult, setMaxResults. Now I have no simple way to get count(*) by Criteria. I can only re-compose query condition using hql to count(*). That means I have to compose query condition with two ways:Criteria, Hql. One for getting result, the other for get count(*).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 05:09:23
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-543 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-543 Summary: Add method to return count(*) in Criteria Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: fafnirchen Created: Wed, 10 Dec 2003 11:09 PM Updated: Wed, 10 Dec 2003 11:09 PM Environment: w2k Description: I used Criteria to query and I call method setFirstResult, setMaxResults to return some records instead of return all records. I am not only want to get these records but also want to get the total num of records fit my query condition without setFirstResult, setMaxResults. Now I have no simple way to get count(*) by Criteria. I can only re-compose query condition using hql to count(*). That means I have to compose query condition with two ways:Criteria, Hql. One for getting result, the other for get count(*). --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-12-11 05:09:22
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 11:08 PM
Use the hibernate debug log
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-542
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-542
Summary: print bind value after print sql
Type: New Feature
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1 rc1
Assignee:
Reporter: fafnirchen
Created: Wed, 10 Dec 2003 10:59 PM
Updated: Wed, 10 Dec 2003 11:08 PM
Environment: w2k
Description:
Standard output print sql with ? but not print what value bind these ?.
Example:
select xxx from xxx where id=?
I wanna print string following this sql like that:
bind 1 value : 5
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-11 05:00:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-542 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-542 Summary: print bind value after print sql Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 rc1 Assignee: Reporter: fafnirchen Created: Wed, 10 Dec 2003 10:59 PM Updated: Wed, 10 Dec 2003 10:59 PM Environment: w2k Description: Standard output print sql with ? but not print what value bind these ?. Example: select xxx from xxx where id=? I wanna print string following this sql like that: bind 1 value : 5 --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-12-10 23:02:17
|
The following comment has been added to this issue:
Author: Tim McCune
Created: Wed, 10 Dec 2003 5:01 PM
Body:
So...
Do you have an alternative fix in mind, do you believe this is not a bug, or is it just impossible to fix? :) If cascading drops only work on certain versions of Postgres, it seems like the dialect could figure that out and support it in the appropriate versions.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 5:01 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-10 22:51:16
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 10 Dec 2003 4:50 PM
Body:
No. DatabaseMetadata is a complete PIA and does not work on many platforms.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-540
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-540
Summary: SchemaExport drop fails if constraint names change
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
toolset
Versions:
2.1 rc1
Assignee:
Reporter: Tim McCune
Created: Wed, 10 Dec 2003 1:06 PM
Updated: Wed, 10 Dec 2003 4:50 PM
Environment: Linux, JDK 1.4, Postgres
Description:
Hibernate doesn't use a cascading drop to drop tables. Instead, it tries to remove constraints and then drop the table. However, it seems to be getting the wrong constraint names. Maybe it's trying to drop the constraints with the name that it's about to generate instead of inspecting the database meta data to get the list of existing constraint names?
I have table foo with foreign key constraint fk124fae0f5c6729a (hibernate-generated).
Running schema export produces this:
alter table foo drop constraint FK124FAE0F5C6729A;
drop table foo;
drop sequence hibernate_sequence;
create table Foo (
id INT8 not null,
bar VARCHAR(255) not null,
primary key (id)
);
ERROR - Unsuccessful: create table Foo (id INT8 not null, bar VARCHAR(255) not null, primary key (id))
ERROR - ERROR: Relation 'foo' already exists
Notice that the constraint name that SchemaExport is trying to drop doesn't even exist. SchemaExport should either get the constraint names from the database metadata or just do a cascading drop. I'm attaching a patch to do the cascade, which is what I'm using locally.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-10 22:46:17
|
The following issue has been updated:
Updater: Jan Blok (mailto:jb...@se...)
Date: Wed, 10 Dec 2003 4:44 PM
Comment:
added cvs patch file
Changes:
Attachment changed to hibernateDDL.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-541&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-541
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-541
Summary: DDL Enhance for drop column and schema usage fix
Type: Patch
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.1 beta 5
Assignee:
Reporter: Jan Blok
Created: Wed, 10 Dec 2003 4:43 PM
Updated: Wed, 10 Dec 2003 4:44 PM
Environment: Hibernate-2.1, all dbs
Description:
[enh]-add Table.sqlAlterDropColumn method and enhance all dialect to support this new feature
[bug]-tablemetadata.initColumns does not use local schema field but
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-534
[bug]-TableMetadata does not take the schema in the hash key for entries in tables map (is little related to previous)
[enh]-add method to Table which constructs/returns schema.tablename
[enh]-overload Table constructor with one to supply all required arguments at once (like schema and table name)
[enh]-Table.sqlAlterStrings rename to sqlAlterAddColumnStrings
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-12-10 22:44:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-541 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-541 Summary: DDL Enhance for drop column and schema usage fix Type: Patch Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.1 beta 5 Assignee: Reporter: Jan Blok Created: Wed, 10 Dec 2003 4:43 PM Updated: Wed, 10 Dec 2003 4:43 PM Environment: Hibernate-2.1, all dbs Description: [enh]-add Table.sqlAlterDropColumn method and enhance all dialect to support this new feature [bug]-tablemetadata.initColumns does not use local schema field but http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-534 [bug]-TableMetadata does not take the schema in the hash key for entries in tables map (is little related to previous) [enh]-add method to Table which constructs/returns schema.tablename [enh]-overload Table constructor with one to supply all required arguments at once (like schema and table name) [enh]-Table.sqlAlterStrings rename to sqlAlterAddColumnStrings --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
93 messages has been excluded from this view by a project administrator.
