Webboard: Perl Frontend

[A.Barkov]

Author: A.Barkov
Email: [EMAIL PROTECTED]
Message:
Please visit this page:

  http://sajnag.org/perl/

It's the home page of a new perl front-end  written
by  Dubun Guillaume.
It supports all mnogosearch databases and modes.


> The current perl frontend is only compatible with MySQL (it actually interfaces 
>directly with the MySQL databases and does not utilize the search.cgi executable at 
>all). I don't know what the architecture of the built in database is, but it's 
>conceivable that a perl script could be written to work with this (or even just 
>regurgitate the output from search.cgi...)
> 
> --Steve 

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Re: Webboard: Perl Frontend

[Danil Lavrentyuk]

[ On Sun, 3 Jun 2001, Steve wrote: ]

S> The current perl frontend is only compatible with MySQL (it actually interfaces 
directly with the MySQL databases and does not utilize the search.cgi executable at 
all). I don't know what the architecture of the built in database is, but it's 
conceivable that a perl script could be written to work with this (or even just 
regurgitate the output from search.cgi...)

It probable will be more useful nother perl frontend, Mogosearch.pm module
written by:
" Copyright (C) 2000, Gecko. http://www.gecko.fr/ "

This module is written as .xs-interface to libudmsearch library.


Danil Lavrentyuk
Communiware.net
Programmer

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Webboard: Perl Frontend

[Steve]

Author: Steve
Email: [EMAIL PROTECTED]
Message:
The current perl frontend is only compatible with MySQL (it actually interfaces 
directly with the MySQL databases and does not utilize the search.cgi executable at 
all). I don't know what the architecture of the built in database is, but it's 
conceivable that a perl script could be written to work with this (or even just 
regurgitate the output from search.cgi...)

--Steve 

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Webboard: Perl Frontend

[marcio]

Author: marcio
Email: 
Message:
Would it work for people using the "built-in database" or just when MySQL etc is used ?

marcio

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Webboard: Perl Frontend

[Steve]

Author: Steve
Email: [EMAIL PROTECTED]
Message:
I've been slowly refining the Perl frontend and have found some problems... The most 
significant right now is that the current SELECT statement in udmDB module to retrieve 
result docs does not handle relevancy correctly. If the following statement is used 
instead, things are better:

SELECT url.url, url.title, url.txt, url.content_type, url.docsize,
   from_unixtime(url.last_mod_time,'Y-m-d h:i:s') as last_mod_time,
   url.keywords, url.description, url.crc32,
   dict.url_id,
   (SUM(dict.word in ($w)) + SUM(dict.intag)) as r, 
   ($qu) as qu 
FROM dict, url 
WHERE dict.word in ($w) AND 
  dict.url_id in ($url_in) AND 
  dict.url_id = url.rec_id 
GROUP BY url_id HAVING qu > 0 
ORDER BY r DESC

The important change is that I've added (+) the sum of word weights to the sum of the 
number of occurrances.

Any suggestions on further improving this query to better mimic the search executable??

When I complete updating the Perl frontend, I will pass along the revised sources if 
that would be desirable to someone.  

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Webboard: Perl Frontend (3.1)

[Steve]

Author: Steve
Email: [EMAIL PROTECTED]
Message:
I've just somewhat resolved my issue # 2 involving the output format, by simply 
removing the other two formats (short and URL) from the template... However, I'm still 
interested in a better way to control this (compatible with the original intention -- 
which was to allow for the dynamic control of the output format, possibly with a 
drop-down on the search form...)

I'm sure if I spend some time in the source I'll be able to get my head wrapped around 
this. However, I'm new to the sources and any pointing in the right direction would be 
greatly appreciated!

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]

Webboard: Perl Frontend (3.1)

[Steve]

Author: Steve
Email: [EMAIL PROTECTED]
Message:
While testing the Perl frontend I've run into two issues:

[1] The results appear to be returned basically with the order reversed compared to 
the C CGI (search.cgi). In addition, the top (#1) result returned by the C CGI is 
returned as the 17th result by the Perl frontend in my test?? (I performed the same 
query with both the standard C CGI and the Perl frontend, which returned 27 results: # 
1 on C interface was # 17 on Perl, # 2 on C was # 27 on perl, # 3 on C was # 26 on 
perl, and so on...) Does anyone have any comments regarding this behaviour??

[2] So far I can only get the results returned in the URL only output format with the 
Perl frontend. The C frontend returns in the long format and both frontend are using 
the same search.htm template file (perhaps I'm doing something wrong or have missed a 
config option)?

Is the PHP frontend preferred over the Perl frontend for some reason? It would be 
difficult for me to recompile the PHP interpreter to include mnoGo support, which is 
why I find the Perl frontend attractive.

Thanks!

Reply: 

___
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]