by Quade (Posted Thu, 12 Sep 2013 09:13:22 GMT)
I don't think you can. For performance reasons, what's loaded when you look at a post list is just a summary of what's on disk. It just knows "has pars" and "doesn't have pars". It doesn't know what the names of the PARS are. So, you can't search for pars because their names aren't even in memory. I think you might be stuck making a single NZB for everything in the date range, then parsing through the single NZB, pulling out the PAR2's you want. Basically generating you own NZB's from the source NZB. If you take the Header and footer from the main NZB and paste in, sections, it should be relatively easy for you to pull fill "FILES" out and generate new NZB's from the data.
The other option would be to use "SQLITE" to pull the data directly from the StorageData.db3 file and generate NZB's from that.
You might be able to make it happen by selecting all the files and expanding them but, I've not tried that and expanding all the files of a large listing can easily eat your ram.
Read Main Topic
I don't think you can. For performance reasons, what's loaded when you look at a post list is just a summary of what's on disk. It just knows "has pars" and "doesn't have pars". It doesn't know what the names of the PARS are. So, you can't search for pars because their names aren't even in memory. I think you might be stuck making a single NZB for everything in the date range, then parsing through the single NZB, pulling out the PAR2's you want. Basically generating you own NZB's from the source NZB. If you take the Header and footer from the main NZB and paste in,
The other option would be to use "SQLITE" to pull the data directly from the StorageData.db3 file and generate NZB's from that.
You might be able to make it happen by selecting all the files and expanding them but, I've not tried that and expanding all the files of a large listing can easily eat your ram.
Read Main Topic