We said bye-bye to SEARCH, now we say bye-bye to INCLUDE at least for TopicFunctions.
By default the DBCacheContrib stores the complete topic text along any formfield
values. Obviously, topic sections (fragments that are extracted using INCLUDE) can
be pre-compiled and stored for faster access so that text extraction
and rendering time during "view" is minimized. The database itself is updated
after a "save" action.
To access these "stored procedures" we introduced a new tag called DBCALL whose
special purpose is to ease the call to TopicFunctions.
The multitude of features of INCLUDE has been
reduced to a reasonable set just to serve the desired purpose. Features that
have been dropped are: pattern extraction, alternative texts when a warning occurs
and fetching off-site pages. That aside DBCALLs can be done recursively as INCLUDEs;
calls can be parametrized; it obeys STARTINCLUDE, STOPINCLUDE, SECTION and
ENDSECTION.
Applying DBCALL to the BlogUp TWikiApplication has been a simple and straight forward
substitution without any extra provisions.