Author |
Topic  |
|
Deleted
deleted
    
4116 Posts |
Posted - 09 August 2001 : 16:31:53
|
First I tought it was a date issue but than I see its not! As nobody else reported this (or I cannot get it from search:) I report it here.
Tested it with my signature `think pink` (to find my posts - all words selection). a) with no restriction I get 7 results (only in internationalization forum) b) if I restrict the search to `Help: General` forum I get 17 results (these were not shown on the previous test)
Any other setting (date limits etc) again give unpredictible results/ You can reproduce the effect.
Thus this is why I`m missing some posts (in addition to a similar active.asp bug).
Think Pink
ADDENTUM:
Just looked at the code of v3.3_02. The SQL near line 109 has strTablePrefix and strActivePrefix prefix mixed. Shoudn`t all be strActivePrefix?
Edited by - bozden on 09 August 2001 16:51:03
Edited by - bozden on 09 August 2001 17:18:53 |
|
gor
Retired Admin
    
Netherlands
5511 Posts |
Posted - 10 August 2001 : 00:45:29
|
You tried this here at the site ? Because then I understand it:
I placed a TOP 50 restriction on the sql statement so it wouldn't time out that often. But, since the current search doesn't use scoring to order, but just topic_id and it counts replies to a topic it finds with those 50 it can happen that you hit the limit with a couple of topics that have a lot of replies.
You might want to try/use the new searchpage I've been working on for the site here. See if that gives better results.
quote:
ADDENTUM:
Just looked at the code of v3.3_02. The SQL near line 109 has strTablePrefix and strActivePrefix prefix mixed. Shoudn`t all be strActivePrefix?
No, that is no error: strSql = strSql & " FROM ((" & strTablePrefix & "FORUM LEFT JOIN " & strActivePrefix & "TOPICS "
Because there is not FORUM_A_FORUM, only a FORUM_FORUM and there are two tables for the topics: FORUM_A_TOPICS and FORUM_TOPICS so there the strActivePrefix is needed to decide which one to use.
Pierre Join a Snitz Mailinglist |
 |
|
Deleted
deleted
    
4116 Posts |
Posted - 10 August 2001 : 04:57:53
|
quote:
You tried this here at the site ? Because then I understand it:
Yes for sure.
quote:
I placed a TOP 50 restriction on the sql statement so it wouldn't time out that often. But, since the current search doesn't use scoring to order, but just topic_id and it counts replies to a topic it finds with those 50 it can happen that you hit the limit with a couple of topics that have a lot of replies.
But if the limit is 50, this does not explain the number 17 & Int. forum.
quote:
You might want to try/use the new searchpage I've been working on for the site here. See if that gives better results.
Yes the results are better, but with the default settings I get very old posts first. Will it be better to sort by posting time and then limit?
quote:
ADDENTUM:
Just looked at the code of v3.3_02. The SQL near line 109 has strTablePrefix and strActivePrefix prefix mixed. Shoudn`t all be strActivePrefix?
No, that is no error: strSql = strSql & " FROM ((" & strTablePrefix & "FORUM LEFT JOIN " & strActivePrefix & "TOPICS "
Because there is not FORUM_A_FORUM, only a FORUM_FORUM and there are two tables for the topics: FORUM_A_TOPICS and FORUM_TOPICS so there the strActivePrefix is needed to decide which one to use.
Pierre Join a Snitz Mailinglist [/quote]
I know that the search related problem does not rely on this. Didn't check the archiving code yet... Sorry if I'm wrong but, if search in archives is set, there can be a problem I think.
Think Pink |
 |
|
msperry
Starting Member
USA
48 Posts |
Posted - 04 January 2002 : 15:27:23
|
There is a problem if search in archives is set.
I get the following:
ADODB.Field error '800a0bcd'
Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
/forum/inc_activeusers.asp, line 90
I did a search within the forum and included archived topics as well. I then clicked on one of the archived topics that the search came back with and I got the above error.
This is in version 3.3.03.
|
 |
|
|
Topic  |
|