NightWind's Card Searcher

Okay a few things.

Second test site

The code cannot and will not handle "find all less than" or "find all more than" searches.
It will now only handle a price range search (alert boxes added). This is because if we were to search for only those less than say, 20, it would return a large number of results. Same goes if you were to search for those above 20 or 40 or whatever. Think of it this way: a large pile of counters when divided by 2 will still result in large piles either way. With such a large number of card results, the code will timeout. The server I'm on isn't the best in the world. More about price ranges below.

Price range will have to be reasonable
A price range of 20 - 40 would result in a timeout
A price range of 20 - 25 would return results
A price range of 30000 - 40000 would return results

Let me know of any price ranges which cause timeouts, but you feel that they are important to warrant a fix attempt.

Hopefully, you'll start to notice the emphasis I'm trying to make - it's not the actual price range which can cause a timeout, but rather the potential number of cards that are returned.

If you do suffer a timeout, try reducing the difference between the highest and lowest price till you get results. If you want a large range of results (which I'm not really sure why you do), try to split it up into a few sub ranges for the search. The server that this is hosted on is in no way a fast server - it's just minimal enough for free users like us.

Timeouts and the like
If you do suffer a timeout, there's no need to worry - you didn't crash all the servers or anything. The nofeehost servers automatically reset themselves every few hours, so if anything bad does happen the impact isn't too lengthy. If the server does happen to go down, you will notice that the search page (default.asp) doesn't even load at all. There could be a possibility that something of this severity could happen. If it does, let me know.

Debug mode
Currently, the second test site is in debug mode. I will be turning off debug if and when I move it to the main site. This mode lets you gauge how many cards are returned before the code crashes.

Misc
Haplo - what price range did you originally search with that caused the timeouts? This info will let me know if I'm attacking the right problem.

Haplo - Also, can you let me know what you're going to use this feature for? Is it to search for expensive cards? Balance data? Curiousity? Statistical analysis? Knowing the intended purpose might let me code this better to suit you.

Everyone who reads this - What would you be using this feature for? Will you be using this at all? I will need to see if this is feasible enough to move onto the main site or should it be dropped (as this code does run a risk of reducing uptime for others).

I will still need to look at the bug with with Raindeer card and seller results. Looks like it's got fleas.


(Dammits I lost my post! Must control anger... ><)

There could be some things I forgot here.