Database pruning support about lasttime HOT 2 CLOSED

Finally ran into an issue that's causing me a little bit of trouble here since the last commit. It turns out that prune_prior_to_date is, at some point, converted into a human-friendly value when passed between the needing verification view of prune_database_by_date and the verified view, where it needs to be utilized in order to correctly assemble a database query and delete the entries in question. Since it doesn't always parse correctly now around line 408 of the previous commit (prune_prior_to_date = datetime.strptime(request.POST['prune_prior_to_date'], '%Y-%m-%d %H:%M:%S')), we're now unable to delete the records in question.

Whoops, strike that about where it's found in the previous commit, it'll be line 408 in the upcoming commit.

from lasttime.

It should be noted that when the records to purge have not been verified the user is redirected to the original pruning results page, but without any of the context information populated, resulting in an unpopulated view.

from lasttime.