Author: michiel
Date: 2010-04-20 15:12:46 +0200 (Tue, 20 Apr 2010)
New Revision: 41974
Modified:
mmbase/branches/MMBase-1_9/example-webapp/src/main/webapp/WEB-INF/web.xml
Log:
MMB-1653 (default searchdir)
Modified:
mmbase/branches/MMBase-1_9/example-webapp/src/main/webapp/WEB-INF/web.xml
===================================================================
--- mmbase/branches/MMBase-1_9/example-webapp/src/main/webapp/WEB-INF/web.xml
2010-04-20 13:12:18 UTC (rev 41973)
+++ mmbase/branches/MMBase-1_9/example-webapp/src/main/webapp/WEB-INF/web.xml
2010-04-20 13:12:46 UTC (rev 41974)
@@ -116,7 +116,20 @@
<param-value>false</param-value>
</context-param>
+ <!--
+ When creating a query, it is not necessary to specify which of the path
elements are on wich side of the join via insrel. Using the allowed
+ relations in 'typerel' this will be implicitely corrected to the correct
value. If _both_ directions are possible, and it is not specified,
+ then MMBase used to fall back to implementing precisely that, so it
would add OR's to the query to make both possibilities match.
+ The disadvantage of that, is that it most of the time performs very
badly in the database. So this implicit fall back direction can be configured.
+ If you set it to 'DESTINATION' then if not specified, and both
directions are possible, it takes 'DESTINATION'.
+ -->
+ <context-param>
+ <param-name>mmbase.defaultRelationStepDirection</param-name>
+ <param-value>DESTINATION</param-value>
+ </context-param>
+
+
<!--
Whether URL's generated to images must include a filename.
Possible values are: 'yes' (from filename field, or from title), 'no',
or '' (only if the 'filename' field is present, and filled).
_______________________________________________
Cvs mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/cvs
