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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: robert [Submitted to the original trac issue database at 8.59am, Wednesday, 11th September 2013]
Here's a little feature request for something that would be useful:
The ability to update a replication to an arbitrary point in the past (after the current planetdir state of course) rather than "now" as it currently always does.
This would be very useful when trying to e.g. sync two planet extracts to the same point in time.
Would also mean those of us testing our application's replication process could slowly trickle data into our database for quick testing turnaround, instead of "oh, I haven't synced this machine's database for 4 days" and having to wait for a massive change to be imported just to test a 3 line change.
Easy?
The text was updated successfully, but these errors were encountered:
Reporter: robert
[Submitted to the original trac issue database at 8.59am, Wednesday, 11th September 2013]
Here's a little feature request for something that would be useful:
The ability to update a replication to an arbitrary point in the past (after the current planetdir state of course) rather than "now" as it currently always does.
This would be very useful when trying to e.g. sync two planet extracts to the same point in time.
Would also mean those of us testing our application's replication process could slowly trickle data into our database for quick testing turnaround, instead of "oh, I haven't synced this machine's database for 4 days" and having to wait for a massive change to be imported just to test a 3 line change.
Easy?
The text was updated successfully, but these errors were encountered: