On 13.07.2012 14:22, Tupy... nambá wrote:
> Wenn man die Vorschlage aus Herrn Gödde folgen wird, man kann ein
> "Googler" bauen. d.h., wenn man "insert" oder "update" macht,
> dann eine Tabelle mit Suchwörte und Index wird aktualiziert..
> stimmt das ?
Genau, but don't forget the "delete"
12 1:22 PM
Subject: Re: [firebird-support] Slow query with like '%xxx%' clause
Wenn man die Vorschlage aus Herrn Gödde folgen wird, man kann ein "Googler"
bauen. d.h., wenn man "insert" oder "update" macht, dann eine Tabelle mit
Suchwörte und Inde
y be better stay with the current search results.
Think about.
Roberto Camargo,
Rio de Janeiro/BR
From: Frank Schlottmann-Gödde
To: firebird-support@yahoogroups.com
Sent: Thursday, July 12, 2012 12:43 PM
Subject: Re: [firebird-support] Slow query with lik
On 07/12/2012 03:17 PM, peixinhosdalua wrote:
> Regarding your suggestions, i need to make a search by '%word%' not 'word%'.
> For example, most companies have a commercial name or brand that they use and
> these are different from the juridic name. It is the juridic name that is
> inserted in
On 12-7-2012 16:24, Tupy... nambá wrote:
>
>
> Caro "peixinhosdalua",
>
> There is no way to increase such kind of searches in a database, because
> the searches are made line per line, searching inside each line by the
> occurrence of your needed search by displacement of the searching word,
tip and no trick to increase the speed.
Good luck, best regards,
Roberto Camargo,
Rio de Janeiro/Brasil.
From: peixinhosdalua
To: firebird-support@yahoogroups.com
Sent: Thursday, July 12, 2012 10:17 AM
Subject: [firebird-support] Slow query with like '%xxx%
Forgot the view!
First task is rewrite the sql only for clientes table.
Try it first and you will not a much better performance.
Next step join the other tables but not using a view.
Finally if it continue slow try changuing your sql to:
Where (clientes.name like 'test%' or clients.name like '%test
Hello,
I made a few query to count the time. I tried with the CLIENTES having 3553
records and with 1000 records. The changes in time performance is significant!
Note that now i am not testing with the VIEW (so not having any joined tabled).
30 SEG (3553 records) 9 SEG (1000 records) (with the
