[x] Allow selecting from multiple "table names" per datalogger in the UI
[x] Allow lookup of table name for each equivalency table
[x] Will require pre-parsing errors to be routed directly to datalogger, use magic string for table_name, for example "preparsed"
Is your feature request related to a problem? Please describe.
Equivalency tables currently have a one-to-one relationship with dataloggers. Each datalogger should instead have multiple table_names, which each map to a respective equivalency table.
Describe the solution you'd like
have a separate "preparsed" table name where all most recent errors and raw json previews fall to help with troubleshooting
datalogger_table table, many to one relationship with table names for each datalogger
use blank string entry in datalogger_table table to signify since it already has the unique constraint for preview and errors "most recent" payloads
The gotcha here is, this table_name field cannot be blank, otherwise it will overwrite the data
Instead, have the program check if the table name is an empty string and return an error if so.
Add GET endpoint for fetching all tables for a datalogger by datalogger_id, just returns data_table uuid, table_name, and errors (array of strings)
Fetch field mapping table and raw data preview when table_id GET is sent
Describe alternatives you've considered
One solution to this would be to require the table name to be added to each URL, but that would require all table names to be url encoded (no spaces or special characters)
Another option would be to simply not log errors prior to binding to the request. The only errors to display would be related to equivalency table mapping (after the request body has successfully bound to the struct). But here you are losing valuable troubleshooting functionality.
Feature Request Type
table_name, for example"preparsed"Is your feature request related to a problem? Please describe.
Equivalency tables currently have a one-to-one relationship with dataloggers. Each datalogger should instead have multiple
table_names, which each map to a respective equivalency table.Describe the solution you'd like
datalogger_tabletable, many to one relationship with table names for each dataloggerdatalogger_tabletable to signify since it already has the unique constraint for preview and errors "most recent" payloadstable_namefield cannot be blank, otherwise it will overwrite the dataDescribe alternatives you've considered
One solution to this would be to require the table name to be added to each URL, but that would require all table names to be url encoded (no spaces or special characters)
Another option would be to simply not log errors prior to binding to the request. The only errors to display would be related to equivalency table mapping (after the request body has successfully bound to the struct). But here you are losing valuable troubleshooting functionality.