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

Replace Internal Database #56

Open
milo-trujillo opened this issue Dec 30, 2017 · 0 comments
Open

Replace Internal Database #56

milo-trujillo opened this issue Dec 30, 2017 · 0 comments
Assignees
Labels

Comments

@milo-trujillo
Copy link
Member

The database storing cameras for Where are the Eyes is overly complicated, inefficient, and easily improved upon.

We've been using marshaled arrays of pin objects, saved to disk in a series of zone files, so we at least don't need to load all the cameras every time any lookup occurs. It was always a terrible database, which we only used so we could focus on prototyping other areas the server more quickly.

We can make things much simpler and faster with a SQLite database, probably with a schema like:

Latitude Longitude Type Location Verifications
3.117... 2.998... Dome Outside <binary_blob>

The type and location fields allows us to satisfy #49, which is part of #3 and #15.

Once we have a SQL table we can do queries like "Get all cameras between these latitudes and longitudes", which makes it easy to isolate nearby cameras, and should make solving #47 trivial.

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

No branches or pull requests

1 participant