You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want entries in the AdlerData database to have their own AdlerID number? Currently the unique identifier for each row is a timestamp, which is useful information to have, but not the most efficient data type for indexing/searching/sorting.
The text was updated successfully, but these errors were encountered:
If we go down the multi-apparation route then we may have more than one entry in the AdlerDatabase with the same ssObjectId, so this would be handy, as we probably shouldn't use MJD timestamps as IDs.
Do we want entries in the AdlerData database to have their own AdlerID number? Currently the unique identifier for each row is a timestamp, which is useful information to have, but not the most efficient data type for indexing/searching/sorting.
The text was updated successfully, but these errors were encountered: