You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: