This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 308
shouldn't archived users be unclaimed? #2472
Labels
Comments
Seems like what we want to do is start using |
Another 10,374 accounts are in the absorptions table and have claimed_time null. |
They result in a 404: https://www.gittip.com/c94df7c6b3c6/. |
Presumably from here. |
So let's see if we have claimed events for the 863 orphans with claimed_times. |
We do! This returns 863 results: select * from events
where payload->>'action'='claim'
and (payload->>'id')::bigint in (
select p.id from participants p
join absorptions a on p.username = a.archived_as
where claimed_time is not null
); |
So we can set |
And then we can set |
chadwhitacre
added a commit
that referenced
this issue
Jun 5, 2014
The take_over code didn't clear claimed_time during archive, but it should have. See #2472. The final-gift.py script *did* clear claimed_time, and our archive method now does the same. The branch.sql here clears out claimed_time for old archived participants (see #2472 for discussion); it needn't be appended to schema.sql since it modifies data and not schema.
chadwhitacre
added a commit
that referenced
this issue
Jun 6, 2014
The take_over code didn't clear claimed_time during archive, but it should have. See #2472. The final-gift.py script *did* clear claimed_time, and our archive method now does the same. The branch.sql here clears out claimed_time for old archived participants (see #2472 for discussion); it needn't be appended to schema.sql since it modifies data and not schema.
chadwhitacre
added a commit
that referenced
this issue
Jun 6, 2014
It was a data update, so no need to append to schema.sql.
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now when we archive users during
take_over
we leave theirclaimed_time
alone. This results in orphan accounts like https://www.gittip.com/74e0d6d7b20a/. Right now we have 863 of these. Why not set claimed_time to NULL during take_over archiving? Because we don't want to lose some info or something?The text was updated successfully, but these errors were encountered: