Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0005946 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Openbravo ERP] A. Platform | major | have not tried | 2008-11-13 10:09 | 2009-05-22 19:33 | ||||||
| Reporter | networkb | View Status | public | ||||||||
| Assigned To | iciordia | ||||||||||
| 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 | ||||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0005946: When an update.database fails you shouldn't be able to acess to the application. | ||||||||||
| Description | -When you do an update.database after solve conflicts depending on how did you solve conflicts the process can fails becausesome constraints can not be enabled. -In this case the update.database process is stopped but you can access to the application. Accessing to the application in this situation can be dangerous because you are able to delete rows of tables were the constraints are not enabled and you shouldn't be able to do this. -I think that you shouldn't access to application until you have solve problems and have done a successfully update.database. -When the process of updating.database fails, a new column in a table of the application could be filled saying that the application is not enabled. Then the login process should check this column to permit or avoid access to the application. This verification could be extended to the export.database process. For example, avoid to do an export.database until you have done a successfully update.database. | ||||||||||
| Tags | ReleaseCandidate | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0010277) jpabloae (reporter) 2008-11-14 11:15 |
A suggestion: Sometimes a "BUILD SUCCESSFUL" doesn't guarantee that all the update.database operations have been successful. Because of this, it could be good to add a "sanity check" after every update.database command, so it could verify that all the constraints are correctly enabled, for instance. If this sanity check fails, we could add a warning or prevent the access. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-11-13 10:09 | networkb | New Issue | |
| 2008-11-14 11:15 | jpabloae | Note Added: 0010277 | |
| 2008-11-26 17:17 | pjuvara | Project | @4@ => Openbravo ERP |
| 2008-11-26 17:17 | pjuvara | Tag Attached: ReleaseCandidate | |
| 2008-11-26 17:17 | pjuvara | Assigned To | => pjuvara |
| 2008-11-26 17:17 | pjuvara | Status | new => acknowledged |
| 2008-11-26 17:18 | pjuvara | Category | => A. Platform |
| 2008-12-02 13:02 | jaimetorre | sf_bug_id | 0 => 2377111 |
| 2009-05-22 19:33 | pjuvara | Assigned To | pjuvara => iciordia |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |