Forums / General / Advanced search bug in 3.2?

Advanced search bug in 3.2?

Author Message

Roy Viggo Pedersen

Friday 03 October 2003 6:43:22 am

When you go to advanced search in a 3.2 site, like http://www.ez.no/content/advancedsearch/ it search for the string "", even if the SearchText parameter don't exist.

Is this a bug?

I guess it's related to this bug: http://www.ez.no/developer/ez_publish_3/bug_reports/advanced_search_empty_string_but_class_qualified_should_be_allowed

Roy

Jan Borsodi

Friday 03 October 2003 7:34:37 am

It's not a bug, read this:
http://ez.no/developer/ez_publish_3/bug_reports/empty_search_causes_slowdown_of_site
by default empty searched are not allowed

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Tony Wood

Tuesday 07 October 2003 8:39:15 am

Jan,

In the bug description you say that the mySQL table is locked until the copy is complete. Is this you doing this in code? mySQL should only lock tables that it is updating http://www.mysql.com/doc/en/Locking_methods.html so I was wondering why this situation occurs.

Would http://www.mysql.com/doc/en/CREATE_TABLE.html Create temporary table help as this create a table for the current connection only?

Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Jan Borsodi

Wednesday 08 October 2003 1:16:08 am

No it's not our code that locks it. The reason for the lock is the behaviour of tables that are of type MyISAM.
The table will lock any UPDATEs if a SELECT is running. It can also lock INSERTs in some cases.

To avoid this problem you can change the table type of the ezcontentobject (and probably some others that are referred in the search) table to InnoDB, however this probably causes every other operation to be slower.

What probably needs to be done is to rethink the search engine, maybe create a new search handler which does things a different way. We also though about having a MySQL specific handler which uses the full text search support in the newer MySQL.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Tony Wood

Wednesday 08 October 2003 2:26:37 am

Forgive me, I see the problem.
http://www.mysql.com/doc/en/Table_locking.html

I love this solution. "Try to get the SELECT statements to run faster." - We should give mySQL guys a prize for this ;-)

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future