export-import: preserve internal ids on export#5762
export-import: preserve internal ids on export#5762tgahunia05 wants to merge 35 commits intomasterfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5762 +/- ##
==========================================
- Coverage 86.54% 85.96% -0.58%
==========================================
Files 1437 1620 +183
Lines 64014 73601 +9587
Branches 7843 8796 +953
==========================================
+ Hits 55402 63273 +7871
- Misses 8392 10103 +1711
- Partials 220 225 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Benchmark ResultMaster commit hash:
Other queries
|
6afe3ca to
9608216
Compare
113484e to
6746660
Compare
|
The failing tests are passing when run in the test splitter. I will spend some time investigating why the testing framework is failing. |
b950e90 to
d389689
Compare
|
Internal id is made up of a table id and an offset. |
Description
When exporting a db there is no guarantee that on import internal ids are persevered. We can change this by (always) exporting the schema.cypher file in order of internal ids
when the user passes a flag to do so.Fixes (#5713)