| Anonymous | Login | 2024-04-25 04:29 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0001056 | ClearOS | app-resource-report - Resource Report | public | 2013-03-26 10:14 | 2019-12-16 08:52 | ||||
| Reporter | user2 | ||||||||
| Assigned To | NickH | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0001056: Check database initialization before running data insert | ||||||||
| Description | The anaconda/installer environment is skipping over the database initialization for some anaconda-reason. No matter, an initialization check should be done before every data insert -- that's more robust. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0012521) NickH (developer) 2019-12-16 08:52 |
The reports tables automatically initialise when they are used. The reports database does not do a robust check (I deleted it and the tables never got created). This may be because of the way I deleted the database, way outside of ClearOS so an "initialised" flag may have been left behind. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-03-26 10:14 | user2 | New Issue | |
| 2013-03-26 10:14 | user2 | Issue generated from: 0001055 | |
| 2013-03-26 10:15 | user2 | Status | new => confirmed |
| 2019-12-16 08:52 | NickH | Note Added: 0012521 | |
| 2019-12-16 08:52 | NickH | Status | confirmed => closed |
| 2019-12-16 08:52 | NickH | Assigned To | => NickH |
| 2019-12-16 08:52 | NickH | Resolution | open => fixed |
|
Issue History |