|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
- here is a post which erroniously suggests that I'm replying to myself.
- this tree still is missing this branch
» moderate Mart £ « Planar Asylum
Follow Ups:
Yeah, that erronious message reply problem has been floating around for some time. Usually, it puts in 'img' as the reply poster name. It's very odd as it gets the name from the message form and that data comes before the message dialogue so it's got to be there. Any ideas as to what you did on that post that might have been different or anything that seemed strange?The second problem was caused originally by a corrupted table and then I had db lock that was causing a script timeout which resulted in the same thing. Both of these have been fixed. I could go back and manually edit in this stuff, but it's awfully tedious and didn't seem to be worth the effort.
I thought the search engine would look for standard tags in the left column & confine its search to the right column inside the same table row. At least it seems plausible to me without rewriting anything. Thus, the new search engine page could resemble the inmate system form we fill out. Given this input, do you still think it would require a rewrite?
eg; if you asked for a certain amp, the engine looks for the auto generated ...
(tr)(td align=right width="40%")(b)Amplifier: (/b)(td)
... then examines from there to the next ... (tr)
I don't want to hound you. I just wanted to make sure that you understand my proposition.
» moderate Mart £ « Planar Asylum
That's not how the data is stored. The search field has the entire record in one field with the array keys and values separated by colons with only a space between fields:Moniker: Mart System Name: brother Dan's 3 channel System Rev Date: 2001/08/21/10:10 System Rev IP: 155.218.112.2 Amp: Aragon : 8008×3 BDR : Mark IV cones Preamp: Marantz ......
Also, the keys don't match the labels on the form, eg Amp versus Amplifier. A Slow Message search for 'Speakers: Quad' might work but isn't that robust or realiable as if wouldn't work if the data was 'Speakers: Maggie 1.6, Quad'.
The actual system data is stored in a text file as this app was done before we implemented the db. Searching is supported via a patch to dump the data into a system table that is defined like a message search table. So doing this right requires rewriting the data pieces to use the db and rewriting the search routine to search sub-fields in a new table for systems.
I didn't ask for a picture or anything. Maybe, just maybe, I did a preview or two.
» moderate Mart £ « Planar Asylum
This post is made possible by the generous support of people like you and our sponsors: