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

Refactor the way saving stations works #94

Open
starcraft66 opened this issue Sep 14, 2024 · 0 comments
Open

Refactor the way saving stations works #94

starcraft66 opened this issue Sep 14, 2024 · 0 comments

Comments

@starcraft66
Copy link
Member

At the moment, when we save the stations, all stations are deleted from the database and re-created. This is unnecessarily destructive imo and results in us saving state about stations in separate tables. As a by-product of this change, we should stop saving the station status in a separate table comprised of many boolean fields and simply make it a field on the station itself.

The new behaviour should simply update station position objects in the database and either prune or create stations based on if the new layout has less or more stations than the current one.

Depends on the merge of #93

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

No branches or pull requests

1 participant