Skip to content

Fix Migration #23#438

Merged
derwok merged 5 commits intodevelopfrom
fix/migration-23
Apr 18, 2018
Merged

Fix Migration #23#438
derwok merged 5 commits intodevelopfrom
fix/migration-23

Conversation

@migerh
Copy link
Copy Markdown
Contributor

@migerh migerh commented Apr 17, 2018

This fixes #437 and repairs databases that were broken by the faulty migration.

migerh added 3 commits April 17, 2018 07:15
Without getCollection we get astronomy classes. getCollection() returns
plain documents.
Copy link
Copy Markdown
Member

@derwok derwok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this QUICK fix! Really looks good!

  • Reviewed code with @migerh
  • Performed the following manual test with a seeded DB (we'll call this PR === v1.5.2)
    • Migrate 1.0.2 => 1.5.2 : OK
    • Migrate 1.0.2 => 1.5.0 => 1.5.2 : OK
    • Migrate 1.0.2 => 1.5.1 => 1.5.2 : OK
    • Migrate 1.0.2 => 1.5.0 => 1.5.1 => 1.5.2 : OK
      "OK" means, that I manually & visually checked that all info was still there, I could edit & store old topics, items, details and that "Finalize" worked again.

So when Travis runs green, I'll merge to develop

@derwok derwok merged commit bc26175 into develop Apr 18, 2018
@derwok derwok deleted the fix/migration-23 branch April 18, 2018 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v1.5.0] Migration#23 corrupts existing infoItems in minutes collection

2 participants