Break meFollow

Ever forgotten when you first contacted your loved one over a PM?
Wanted to reminice about your first Cyb0ring on Allakhazam.com?
Want to track down every message some as[cyan][/cyan]shole sent you so you can find them and shoot them?

If so, feel free to test out my new PM Name Searcher!

Now you can go and find out every time your favorite admin has yelled at you helped you out with technical problems!

nifty!

I did a search for a name with over 128 chars (including specials)...the search took 47 seconds to complete, but it didn't error. May want to set the maxlength property of the textbox though.



Confirmed.

Edited, Fri Mar 24 11:00:45 2006 by Frakkor

It just reminded me that I never get any PMs. Does that make me a L00s3r?

Looks like I don't get enough pm's to break it.

I just don't cyper like I used to.

ew, partials! If you don't know somebody's name, too damn bad!

Well, for now at least.

anyone else getting no results for queries? It could just have been a fluke from a stuck query.

If I search for kao* or kao% I get a "No user by that name" message.

If I search for plain "kao" I get the following (pic linky)

Confirmed that the eariler link bug is fixed.

change your SQL = to a SQL like. We'll try to break it again.

Yeah, LIKE works fast enough. Think I need to explain the whole % syntax thing to people?

Or just let those "in the know" use it that way? =P

Edited, Fri Mar 24 12:13:03 2006 by Danalog

In the past, I've just built the wildcards into the query. Depends on if you ALWAYS want them in.

I would not return a list of choices, just the list of results...IMHO.

Kao should be the first result if sorted by name, but yeah, assuming % is something that you'll need to decide to do.

For my projects in the past it made sense.

Perhaps an checkbox that will add in the % if full name isn't known?

Edited, Fri Mar 24 13:26:12 2006 by Frakkor

then no LIKE.

geesh, you could've said that from the beginning!

because I wanted a damn search page!