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

DB: change architecture of locations table #38

Open
sofiia-tesliuk opened this issue Mar 11, 2020 · 1 comment
Open

DB: change architecture of locations table #38

sofiia-tesliuk opened this issue Mar 11, 2020 · 1 comment
Labels
architecture Designing architecture database Database

Comments

@sofiia-tesliuk
Copy link
Contributor

Sort locations by city_id. Don't use field city_id in each location.
This is needed for optimization of GET requests, as we always need locations only from one city.

From

locations: {
    location_id: {
        city_id: int,
        other_location_info ... 
    }
}

To

locations: {
    city_id: {
        location_id: {
            some_location_info ... 
        }
    }
}
@sofiia-tesliuk sofiia-tesliuk added database Database architecture Designing architecture labels Mar 11, 2020
@sofiia-tesliuk
Copy link
Contributor Author

sofiia-tesliuk commented Mar 11, 2020

TODO:

  • Update architecture in Firebase
  • Update functions to manage with new architecture:
    • get_receive_stations()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Designing architecture database Database
Projects
None yet
Development

No branches or pull requests

1 participant