The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 26 Aug 2003 1:24 PM
Body:
Actually, you CAN always name each property of a component or composite id (even in the case of an association).
OTOH, this is a desirable feature, certainly.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-290
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-290
Summary: Allow component in IS NULL HQL
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee:
Reporter: Emmanuel Ligne
Created: Tue, 26 Aug 2003 1:27 AM
Updated: Tue, 26 Aug 2003 1:27 AM
Description:
Allow paths to components (or classes) in IS (not) NULL statement and
not only terminal properties. As long as component types are concerned,
testing "is null" corresponds to testing each column of the component
(or each column of the key for a class), based on the values returned
by the nullSafeSet(null) on the component or key type.
This would allow usage of multi-column ids, as for now these cannot
be used in HQL (cannot name each column as in composite-id).
---------------------------------------------------------------------
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
|
