Filtering files in a VaultHistoryQueryRequest

[mmoayyed]

Well, given the number of folders I have to do this on wouldn't it be faster if I ran one query and filtered everything later ? it seems like running one query for every folder would rather be expensive and exhaustive on performance. Which would you recommend ?

[shannon]

Sorry, you didn't specify how many folders, but given your wording I thought it might only be a handful.

If there are many, then you're right, an individual query on each is probably not the way to go.

How are these folders chosen? I'm just wondering if there's anything else we can filter on to at least reduce your results a bit.

[mmoayyed]

We simply have about 9-10 folders that we'd like to track and write the results to a SQL database. These folders unfortunately do not satisfy a criteria that could be put into the query. The list comes from a database table, with nothing common among them as far as names or paths gom and items can be added or removed from. Going back to my original question, it would be super great if the query accepted a list/array that actually filtered on the object path, folders specifically when it does a recursive search with $ being the top folder name.

[shannon]

I'm sorry, but I don't have any other good suggestions. If you aren't going to be running this often (maybe only once a day or something) it might be worth it to try the 9-10 queries and see how it fares with your tree, it'd certainly be less filtering work for you - otherwise I'd just hit the server once and filter later.

If this were a limitation from the way the api method was written, I could just direct you in writing your own, but the service methods just don't have what you're looking for, because our history query dialog doesn't filter that way.