|
7398260a57
|
Improve SQL statements for getting device reading types
|
2019-11-07 18:43:28 +00:00 |
|
|
a678a89b95
|
Add last_seen to list_devices_near
|
2019-08-14 13:00:30 +01:00 |
|
|
7a489706bd
|
Bugfix new device sensor list
|
2019-07-18 22:18:30 +01:00 |
|
|
a325940322
|
Implement new ISensorRepository.
This is thanks to @BNNorman's recent DB changes :D
|
2019-07-18 21:19:16 +01:00 |
|
|
d5df81eed1
|
Add last_seen to device-info. For 36
|
2019-06-30 17:33:44 +01:00 |
|
|
5efaab3f67
|
Add last-seen to list-devices.
For #36.
|
2019-06-30 17:27:57 +01:00 |
|
|
e86b0b4f97
|
Upgrade ST_DISTANCE() to ST_DISTANCE_SPHERE(), but there's a permissions issue.
|
2019-06-26 21:02:17 +01:00 |
|
|
2d07af950a
|
Use new column name
|
2019-06-23 14:42:47 +01:00 |
|
|
030d0cb9be
|
Revert "Don't use the new datetime computed column until the issues are worked out"
This reverts commit 97e234b920 .
|
2019-06-23 14:39:24 +01:00 |
|
|
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 |
|
|
51c76ccd58
|
Add list-devices-near action with appropriate API documentation
|
2019-06-21 22:05:13 +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 |
|
|
dcdec686a4
|
Add device_type_id output as type_id
|
2019-03-14 12:50:43 +00:00 |
|
|
ac4ecd1751
|
API: Return altitude information
|
2019-03-14 12:42:17 +00:00 |
|
|
519e85b66a
|
[server] Bugfix: Updatee device-data action t use DB structure
|
2019-02-20 17:39:45 +00:00 |
|
|
3c2605dcb9
|
Port the data repeository over to the new structure
|
2019-02-18 20:44:37 +00:00 |
|
|
828e7ad999
|
Bugfix: Update a significant portion of the backend to the new database structure
|
2019-02-18 20:39:35 +00:00 |
|
|
3a2b2571f6
|
[API] Add device-id GET parameter to list-reading-types action..
|
2019-02-07 19:15:38 +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 |
|
|
73cd2a77dc
|
[server/device-info] Actually use the device-id parameter
|
2019-01-18 23:02:24 +00:00 |
|
|
575a6b1dd6
|
[server] Add device-info api call
|
2019-01-18 21:49:14 +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 |
|
|
4a2b8fc3c6
|
[server/list-devices] Tweak prorperty names
|
2019-01-17 15:52:42 +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 |
|
|
57ec980b7d
|
Fix meaurement type repo
|
2019-01-15 16:16:00 +00:00 |
|
|
f31989b7eb
|
Fix repo interface definition
|
2019-01-15 15:58:23 +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 |
|
|
bbd08b439e
|
Create a apir of interfaces for the repositories
|
2019-01-14 21:43:45 +00:00 |
|