1 message in com.perforce.perforce-user[p4] any way to get around maxresults?| From | Sent On | Attachments |
|---|---|---|
| Matt Harp | 17 Sep 2001 08:39 |
| Subject: | [p4] any way to get around maxresults?![]() |
|---|---|
| From: | Matt Harp (mha...@seapine.com) |
| Date: | 09/17/2001 08:39:54 AM |
| List: | com.perforce.perforce-user |
hey all,
I am writing a small app to query the p4 database for all of it's files (p4 files //depot/...). One hurdle I see ahead of me is how to handle doing this when the user has a maxresults limit set. I have two questions regarding this.
1. What percentage of users actually has a maxresults limit set to something other than unlimited (what would you guess the average limit is?)? I have never used Perforce in a production environment, so i'm pretty clueless about how it is used by others.
2. Is there a way to kludge stuff to override that maxresults value for one command call? My initial plan of attack is to check their maxresults value, and if it is not unlimited, then I will call p4 dirs and then do a p4 files call for each directory(although this would slow my app down). I am thinking that this should handle most situations, since I doubt many people will have thousands of files in any given directory. However, the possibility exists that a cmd such as "p4 files //depot/dir/*.*" will still yield too many results. At this point, I am not sure how to proceed. Should I worry about this last scenerio? If so, how can I break the query down further? I can't find any other way to limit the number of rows returned beyond a directory limit.
What are the risks of kludging the call to get around the maxresults limit, if any such kludge exists?
Thanks in advance for any help with this!
-matt




