[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-265?page=all ] Alex Savitsky updated EJB-265: ------------------------------ Attachment: Branch.java Visit.java Issue.java Entity files that generate the described error. The query with error is defined in Issue.java as a named query -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-265?page=all ] Alex Savitsky updated EJB-265: ------------------------------ Attachment: TestCase.zip application.properties Complete test case, as an Eclipse Java project. Oracle JDBC Driver is not included. application.properties need to be placed in src folder, and DB connection info need to be specified in it. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=all ] Emmanuel Bernard updated HHH-2408: ---------------------------------- Version: 3.2.2 (was: 3.2.1) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=c... ] Alex Savitsky commented on HHH-2408: ------------------------------------ My bad for not checking the docs. However, if an operation is not supported, a general expectation is to receive an UnsupportedOperationException (or something alike) at the time the query is parsed (it was a @NamedQuery, so that would be the startup time), rather than a cryptic DB-specific message during runtime execution, wouldn't you agree? Regards, Alex -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=c... ] Steve Ebersole updated HHH-2408: -------------------------------- Component/s: query-hql Fix Version/s: 4.0.0.next Assignee: Steve Ebersole Will have a look -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2408?page=c... ] sebastien michea commented on HHH-2408: --------------------------------------- Steve, I understand this is not supported yet, but why did you close the bug ? Best regards, Sebastien -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-2408?page=com.atlassian.jira.plug... ] Istvan Kovacs commented on HHH-2408: ------------------------------------ By which part of the JPA specification (*not* HQL!) is this 'not supported' (by JPA)? http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-eval-oth-JSpec/... 4.10 update_statement ::= update_clause [where_clause] 4.5 where_clause ::= WHERE conditional_expression 4.6 Conditional Expressions 4.6.3 Path Expressions "It is illegal to use a collection_valued_path_expression within a WHERE or HAVING clause as part of a conditional expression except in an empty_collection_comparison_expression, in a collection_member_expression, or as an argument to the SIZE operator." That is the only restriction on path expressions; the reported update's WHERE clause did not refer to a condition-valued path, so it does not apply. Therefore, the path expression in the WHERE clause is valid, I think. Please let me know if I'm wrong, or if we can expect a fix for the issue (if it's valid). Thanks, Kofa -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-2408?page=com.atlassian.jira.plug... ] Istvan Kovacs commented on HHH-2408: ------------------------------------ Steve, thanks for the quick update. Here is the query: {quote} UPDATE Issue i SET i.dueDate = i.dueDate + 10 WHERE i.visit.branch.id = :branchId {quote} The UPDATE clause is defined as: {quote} UPDATE entity_name [[AS] identification_variable] SET update_item \{, update_item\}* {quote} As far as I see, in this case it's UPDATE Issue i SET i.dueDate = i.dueDate + 10 It appears to me that this contains only one 'entity abstract schema type', namely 'Issue'. Am I mistaken? Thanks, Kofa -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-2408?page=com.atlassian.jira.plug... ] Istvan Kovacs commented on HHH-2408: ------------------------------------ Steve, thanks for the explanation. Maybe an enhancement to reject the invalid query would make this less confusing; generating invalid SQL is hardly the solution. I know, 'garbage in, garbage out', but from another point of view, we expect parsers to validate syntax (e.g. you wouldn't like javac to generate invalid byte code if you make a syntax error in your source). Kofa -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira