Custom Query (1174 matches)
Results (187 - 189 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5369 | fixed | Broken activities cause database migration errors | ||
| Description |
Per the conversion on the devel list, activities which have deleted media cause issues in migrations such as 29 and 42. These migrations expect activity objects or targets to be non-null, so they don't know how to handle activities with deleted objects. |
|||
| #5368 | fixed | Migrations 29 and 35 consume hard drive | ||
| Description |
Per the devel list conversion, database migrations 29 and 35 consume a very large amount of hard drive space on instances with numerous database entries. A proposed solution would be to run db.commit after every entry instead of once at the end. This may make the entire migration slower, but it will hopefully prevent consuming all storage space. |
|||
| #5367 | fixed | Update edit view for database changes | ||
| Description |
Editing other users' media causes a server error. |
|||
Note:
See TracQuery
for help on using queries.
