On Wed, Feb 5, 2014 at 6:03 AM, Stefan Fuhrmann <
stefan.fuhrm...@wandisco.com> wrote:
> On Wed, Feb 5, 2014 at 4:02 AM, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 05.02.2014 03:10, Daniel Shahaf wrote:
>>
>> However, 'load --ignore-dates' has another use-case: preventing the "-r
>> {DATE} doesn't work as intended" syndrome when loading a project's history
>> into an existing repository.
>>
>>
>> I would argue that this is an implementation bug, pure and simple. The
>> fact that it has persisted since svn-1.0 doesn't change anything. There is
>> no reason why -r {DATE} couldn't be made to work regardless of the ordering
>> of the dates; it's just that no-one has taken the trouble to actually fix
>> the filesystem to return valid results in all cases.
>>
>
> That would be extremely expensive to do in the existing backends:
> We would need to effectively read all revision properties of all revs.
> If we added an index ("revision order by time stamp"), we could do
> better but would need to update the index upon every (rev) propset.
>
One more thing. Even with such index, we can only get -r {DATE} to
work but handling the date range {DATE1}:{DATE2} requires massive
changes in the underlying logic and potentially APIs. The reason is
that the date range potentially translates into a sequence of revision
ranges which brakes assumptions of path continuity in e.g. 'svn log'.
-- Stefan^2.
