Closed rpswenson closed 2 months ago
Nothing to delete
is from the delete call to IntervalList
, so we can ignore that. If you find it distracting, we can revisit the delete logic to first check for deletes before running. That would trade off speed for output clarity
Upstream tables
error is our way of protecting data integrity without transactions. More info here. I adjusted the check mechanism in #1108 yesterday. Updating may fix the issue. It may be the case that someone else was working on something upstream at the same time, in which case this is working as intended. If you encounter this issue repeatedly, it could be a bug.
This may work better:
sss_pk = (sgs.SpikeSortingSelection & key).proj().fetch(as_dict=True)
sgs.SpikeSorting.populate(sss_pk)
Please use the bug report template for future bug submissions
okay yeah updating fixed it. apologies
Running this populate for SpikeSorting:
I get this output:
This particular output also has a "nothing to delete" warning but when I first ran into this in my spikesorting loop it did not get that warning, but still had the
Upstream tables changed during non-transaction populate. Please try again.
message