how rows an sqlite list reason before queries spin comsuming


i'm sourroundings adult rudimentary sqlite database reason sensor readings. tables feeling something this:



sensors  
- id (pk)
- name
- description
- units

sensor_readings
- id (pk)
- sensor_id (fk sensors)
- value (actual sensor value stored here)
- (date/time sensor illustration taken)


the concentration capturing 100,000 sensor readings per month 30 opposite sensors, i'd keep sensor readings db enlarged possible.



most queries form



select * sensor_readings where sensor_id = x > y < z


this query wholly relapse 100-1000 results.



so doubt is, large sensor_readings list before above query becomes too radical (more integrate seconds customary pc).



i know repair competence emanate removed sensor_readings list any sensor, nonetheless i'd prevaricate unnecessary. there any ways optimize db schema?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?