Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0037708 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | minor | have not tried | 2018-01-23 18:50 | 2022-02-01 08:08 | ||||||
| Reporter | aferraz | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | SCM revision | ||||||||||
| Merge Request Status | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Support ticket | |||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0037708: Update of Order table not working in HQL | ||||||||||
| Description | If we try to run an update query in Order table using HQL, following error is raised: java.lang.IllegalArgumentException: node to traverse cannot be null! | ||||||||||
| Steps To Reproduce | Create following HQL query: Query updateQry = OBDal.getInstance().getSession().createQuery("update Order set description = 'a'"); You get following error: java.lang.IllegalArgumentException: node to traverse cannot be null! If we create the same query for Invoice table instead of Order table, query is correctly created: Query updateQry = OBDal.getInstance().getSession().createQuery("update Invoice set description = 'a'"); It seems that Hibernate is confusing Order table name with order by keyword. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0102292) alostale (viewer) 2018-02-09 09:27 |
Moving to design defect, as this seems to be a Hibernate restriction [1]. [1] https://stackoverflow.com/questions/3599803/jpa-hibernate-cant-create-entity-called-order [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-01-23 18:50 | aferraz | New Issue | |
| 2018-01-23 18:50 | aferraz | Assigned To | => platform |
| 2018-01-23 18:50 | aferraz | OBNetwork customer | => No |
| 2018-01-23 18:50 | aferraz | Modules | => Core |
| 2018-01-23 18:50 | aferraz | Triggers an Emergency Pack | => No |
| 2018-01-23 18:51 | aferraz | Relationship added | related to 0028330 |
| 2018-01-23 18:52 | aferraz | Relationship added | related to 0028163 |
| 2018-01-23 18:53 | aferraz | Description Updated | View Revisions |
| 2018-01-23 18:53 | aferraz | Steps to Reproduce Updated | View Revisions |
| 2018-01-23 18:56 | aferraz | Steps to Reproduce Updated | View Revisions |
| 2018-02-09 09:27 | alostale | Note Added: 0102292 | |
| 2018-02-09 09:27 | alostale | Status | new => acknowledged |
| 2018-02-09 09:27 | alostale | Type | defect => design defect |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |