Commit graph

19 commits

Author SHA1 Message Date
97e234b920
Don't use the new datetime computed column until the issues are worked out 2019-06-23 13:54:18 +01:00
913786ec0b
Drastically optimise the queries behind fetch-data and device-data. 2019-06-22 21:08:12 +01:00
b4ae0b457b
Optimise some queries using the new datetime computed column, but there's more work to do.
The fetch-data query in particular is using the wrong index.
2019-06-22 11:50:23 +01:00
87c0eb90ba
Optimise the fetch-data query 2019-06-20 22:12:33 +01:00
009e2e4b72
Bugfix new device-recent-data action 2019-06-13 22:10:14 +01:00
dba984340d
Implement new device-data-recent, but it's not working right. 2019-06-13 22:02:04 +01:00
530876ab5f
[server/fetch-data] Omit send device location information 2019-04-16 17:40:32 +01:00
3c2605dcb9
Port the data repeository over to the new structure 2019-02-18 20:44:37 +00:00
ee6cf4a86e
[server] Bugfix: Filter result of device-data action by reading type 2019-01-20 22:03:06 +00:00
39869afea0
[server] Add device-data API action 2019-01-19 21:12:11 +00:00
0cefd047f4
[server] Add device-data-bounds API call 2019-01-19 16:08:47 +00:00
aa88da0617
[server] Tweak measurement data properties 2019-01-17 17:02:22 +00:00
3a62ef08d9
[server/fetch-data] Dedupe records & add property to indicate the # of records 2019-01-17 16:51:37 +00:00
f0781948f3
[server] Add list-devices API action 2019-01-17 15:39:50 +00:00
6123e2c679
Use timediff -> time_to_sec -> abs to make datetime fuzzy 2019-01-15 17:27:35 +00:00
102bd13864
Fix measurement data query (I think) 2019-01-15 17:05:21 +00:00
9f6bea64d4
Fix measurement data query, but it's not quite right yet 2019-01-15 17:02:24 +00:00
dea95716ed
Fill out mesurement type repo methods 2019-01-15 15:57:39 +00:00
cef578d7eb
Implement a bunch of stuff.
Things are coming along fast!
2019-01-15 15:46:24 +00:00