When member_num is missing, ingest always creates a new Driver row. On re-ingest of an existing event (when the axdb hash changes), the code deletes Entry rows but does not delete the corresponding no-member drivers, so repeated ingests can accumulate orphaned/duplicate Driver rows. Consider cleaning up event-scoped drivers without memberNum during re-ingest, or introducing a stable upsert key for those drivers to prevent unbounded growth.
When member_num is missing, ingest always creates a new Driver row. On re-ingest of an existing event (when the axdb hash changes), the code deletes Entry rows but does not delete the corresponding no-member drivers, so repeated ingests can accumulate orphaned/duplicate Driver rows. Consider cleaning up event-scoped drivers without memberNum during re-ingest, or introducing a stable upsert key for those drivers to prevent unbounded growth.