TeeJay (email not shown publicly)
http://www.aarontrevena.co.uk/
Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN :
TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal :
hashbangperl [livejournal.com]
flickr
:
hashbangperl [flickr.com]
Scalar vs. Vector (Score:2)
Not quite. MySQL has a scalar cosine function, like Perl and damn near every other programming language you can name. Because this is a vector based search engine, you need to take the cosine of the two vectors, as the article clearly states:
Re:Scalar vs. Vector (Score:1)
That confirms my initial concerns that it wouldn't scale well, as you would have to do a lot of mathematical grunt work in Perl (or more likely the C PDL library), as opposed to using a specialised tool like a relational database to the bulk of the processing.
I don't think MySQL would manage the cosine math involved here. Oracle probably would using horrid PL/SQL perversions, but that would subtract rather from the initial elegance.
It would be nice to be able to do
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;