Bug 1220749
| Summary: | Saving View Model with syntax error in Transformation breaks it completely | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Andrej Smigala <asmigala> |
| Component: | Tooling | Assignee: | Barry LaFond <blafond> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Andrej Smigala <asmigala> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | atangrin, drieden, mbaluch, mmakovy, vhalbert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-17 18:06:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
recommend push to next patch, 9.0.3 Barry LaFond <blafond> updated the status of jira TEIIDDES-2517 to Resolved Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2517 to Closed |
Saving a view model when there is a syntax error in the transformation can sometimes make it completely broken. Steps to reproduce: 1. create a new view model 2. add a new table t1 to it, with a column c1 3. set the transformation to SELECT 'c1' as c1; 4. add two backslashes to the beginning of the transformation 5. try saving the model (error about wrong syntax error pops up) 6. try saving again 7. remove the backslashes, try saving again (the same error pops up) 8. close the model, answer No to Save resource dialog 9. open the model again, try opening the transformation – the model is broken Going through the steps to reproduce, it appears after the first save, the invalid transformation is not saved to the file, but after saving for the second time, it is. Designer should ideally prevent invalid SQL to be saved to the model. Workaround is to open the model in XML editor and fix the transformation manually.