Currently dbpf_devices_sensors_add "moves" sensors from one device to a new device, the sensors must exist ahead of time.
In contrast, other dbpf_***_add functions are used to add rows directly to other tables, using all the rows present in the table.
We need an easy way to add new devices_sensors rows to the database, and so dbpf_devices_sensors_add should be renamed for consistency and to clearly describe what it does.
Some Ideas:
dbpf_device_swapdbpf_swap_devicedbpf_swap_devices
@hgmacc : any ideas? Am I missing anything?
Currently
dbpf_devices_sensors_add"moves" sensors from one device to a new device, the sensors must exist ahead of time.In contrast, other
dbpf_***_addfunctions are used to add rows directly to other tables, using all the rows present in the table.We need an easy way to add new
devices_sensorsrows to the database, and sodbpf_devices_sensors_addshould be renamed for consistency and to clearly describe what it does.Some Ideas:
dbpf_device_swapdbpf_swap_devicedbpf_swap_devices@hgmacc : any ideas? Am I missing anything?