Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a simpler scheme for safe element IDs #1304

Merged
merged 6 commits into from
Mar 7, 2023

Conversation

jimallman
Copy link
Member

As discussed, we'd like to have single- or double-digit IDs for elements (esp. trees). This scheme will keep track of the highest minted IDs for each element type and store it in phylesystem. Addresses #1302.

As discussed, we'd like to have single- or double-digit IDs for elements
(esp. trees). This scheme will keep track of the highest minted IDs for
each element type and store it in phylesystem.
@jimallman
Copy link
Member Author

I'm still testing this on devtree, so holding it in draft mode for now.

This is important for old/existing studies that have not previously
stashed the last-minted ID for each element type.
@jimallman
Copy link
Member Author

OK, this seems to be working as intended on devtree. Studies now save with accurate highest-minted-id information, reload properly, and skip any minted-then-deleted IDs. Done, I think.

@jimallman jimallman marked this pull request as ready for review February 28, 2023 21:17
@jimallman
Copy link
Member Author

See the history of study tt_266 for a series of test commits.

@mtholder mtholder merged commit ee5deda into master Mar 7, 2023
@mtholder mtholder deleted the store-highest-minted-element-ids branch March 7, 2023 19:06
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.

2 participants