NightWind's Card Searcher

(02-09-2009 05:49 AM)Runemaster Wrote:  Could you do it so that you can't search specifics, only the price range?

That wouldn't improve the situation much. What happens is that it parses the store feed, finds the cards within range and then ORs the cards (hehe, I made a new word). That ORing kills the query. Which is why the search only works for price ranges which return a small number of cards.

(02-09-2009 05:50 AM)masamunemaniac Wrote:  What's the point of a minimum price? I could see why you'd want to know all cards meeting criteria X and costing under 5000 points (you only have 5000 points), but why only cards costing over 1000 points?

*light shrug*

It was supposed to reduce the result set to a more suitable quantity, but even with the minimum price, the cards to be ORed are too many for the query to handle.

Option 1:
I suppose the only solution I have left for now is to split then recombine the queries. Judging by the interest for this feature expressed here, I might as well give it a go this weekend.

Option 2:
On second thought, I could always just get the price range, return the card ids only and then use getcard? That... could very well work. It may mean writing another program module, but that sure beats fiddling with SQL technical restrictions. But do note that this method will not integrate with the other search functions. Thus, you cannot search for all cards cheaper than 2000, and is in the MC expansion.

Feh. From the looks of it, option 2 will eventually point back to option 1... I'll try option 1 this weekend, and resort to option 2 if needed. Thoughts?