On 27.06.2006 13:31, Oleg Bartunov wrote:
On Tue, 27 Jun 2006, Hannes Dorbath wrote:
http://www.symfony-project.com/askeet/21
How does this dead simple approach compare to TSearch performance /
scaling wise?
You miss the main point in tsearch2 - full integration with database, i.e.,
full access to metadata, ACID..... Lucene has no of these features, so
it could use some well known optimization
and, and so, scales better. If you don't need ACID, metadata access, why
do you need database at all ?
Yes, I know the benefits of using TSearch :) (I'm using it on many
projects) I just found that article and wondered how well this simple
approach might scale. Sorry for wasting your time ;)
--
Regards,
Hannes Dorbath
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
