[TYPO3-dam] "Indexing date" issues
Dan Osipov
dosipov at phillyburbs.com
Mon Mar 30 22:48:53 CEST 2009
> We know, how many files have been uploaded, so we can select X files
which
> were created by user X with timestamp >= timestamp of indexing run.
I'm probably missing something obvious, but how do you know how many
files were uploaded after its all done and they're indexed?
> If you're are still for a new field, I'll try to implement this for
1.2 after
> my diploma examination next week.
Good luck!!
Dan Osipov
Calkins Media
http://danosipov.com/blog/
Steffen Gebert wrote:
> Hi Dan
>
> Dan Osipov wrote:
>> > * Modify the selection of indexing date: Don't only use the exact
>> > crdate timestamp, but get the X next files with crdate >=
>> > indexing-crdate. X is already saved in item_count (maybe a hotfix, but
>> > problematic if two
>> runs at
>> > the same time).
>>
>> And what's the cut off time? 10 seconds? 1 minute? And yes, several runs
>> are a problem
>>
>> > * Improvement of the above: Only select X files with same cruser_id
>> as the
>> > index run
>>
>> Same issue as above
>
> Just to explain it a bit more precise: It should work perfectly as long as
> server doesn't index >1 upload jobs of ONE user at the same time.
> We know, how many files have been uploaded, so we can select X files which
> were created by user X with timestamp >= timestamp of indexing run.
>
> I think it's quite hard for a user to finish two uploads at the same time.
> But of course it's possible.
>
> If you're are still for a new field, I'll try to implement this for 1.2 after
> my diploma examination next week.
>
> Regards
> Steffen
>
More information about the TYPO3-project-dam
mailing list