View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000296 | Comica 2 | Backend / Core | public | 2019-01-28 08:32 | 2019-01-29 08:44 |
| Reporter | BootBlock | Assigned To | BootBlock | ||
| Priority | immediate | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 2.00 | ||||
| Target Version | 2.00 | ||||
| Summary | 0000296: Implement a Database-wide metastore | ||||
| Description | Archived image strips have a metastore, as do comic definitions. Because IsFavourite is no longer a property on Comic.Definition (so databases remain untouched by user-specific changes), Database requires its own metastore. | ||||
| Tags | No tags attached. | ||||
|
|
Done. The metadata for a database is stored within the root of the currently-set ArchivalPath and is named after the database's Guid. I have to get out of the mindset that the on-disk files will be manually manipulated by the user and not name them using the human-readable names of comics/databases as there will be issues - like in Comica 1.xx - where if a comic/DB has its name changed, then things break. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-28 08:32 | BootBlock | New Issue | |
| 2019-01-28 08:32 | BootBlock | Assigned To | => BootBlock |
| 2019-01-28 08:33 | BootBlock | Status | new => acknowledged |
| 2019-01-28 08:33 | BootBlock | Relationship added | child of 0000290 |
| 2019-01-29 08:44 | BootBlock | Status | acknowledged => closed |
| 2019-01-29 08:44 | BootBlock | Resolution | open => fixed |
| 2019-01-29 08:44 | BootBlock | Note Added: 0000041 |