As far as I'm concerned nothings going to beat PG's GIS calculations, but it's tsearch was
a lot slower than myisam.

My goal was a single solution to reduce our complexity, but am interested to know if combining
both an rdbms & lucene works for you. Definitely let me know how it goes !

P

Guillaume Smet wrote:
Hi Patrick,

On 9/27/07, patrick o'leary <[EMAIL PROTECTED]> wrote:
  
 p.s after a little tidy up I'll be adding this to both lucene and solr's repositories if folks feel that it's a useful addition.
    

It's definitely very interesting. Did you compare performances of
Lucene with a database allowing you to perform real GIS queries?
I'm more a PostgreSQL guy and I must admit we usually use cube contrib
or PostGIS for this sort of thing and with both, we are capable to use
indexes for proximity queries and they can be pretty fast. Using the
method you used with MySQL is definitely too slow and not used as soon
as you have a certain amount of data in your table.

Regards,

  

--
Patrick O'Leary


You see, wire telegraph is a kind of a very, very long cat. You pull his tail in New York and his head is meowing in Los Angeles.
 Do you understand this? 
And radio operates exactly the same way: you send signals here, they receive them there. The only difference is that there is no cat.
  - Albert Einstein
View Patrick O Leary's LinkedIn profileView Patrick O Leary's profile

Reply via email to