Best point to start debugging for filter/query problems is the dbform tag,
method doStartTag(), somewhere around line 1507. This is named as part III:
         // *************************************************************
         //  Part III - fetching Data. This data is provided to all sub-
         //  elements of this form.
         // ************* 

>From there the searchFields of the form are filled from
initSearchFieldValues().

The filter stuff is done earlier here:

         if (!Util.isNull(getSqlFilter())
                  && !Util.isNull(requestSqlFilterString)) {
            sqlFilterString = " ( " + requestSqlFilterString + " ) AND ( "
               + getSqlFilter() + " ) ";
         } else if (!Util.isNull(getSqlFilter())) {
            sqlFilterString = getSqlFilter();
         } else if (!Util.isNull(requestSqlFilterString)) {
            sqlFilterString = requestSqlFilterString;
         }

         logCat.debug("filter to apply : " + sqlFilterString);

         if (!Util.isNull(requestSqlFilterString)) {
            sqlFilterParams = DbFilterTag.getSqlFilterParams(request,
                  this.getTable().getId());
         }


Parent child filters are build much earlier in part II:

            // If whereClause is not supplied by developer
            // determine the value(s) of the linked field(s)
            if (Util.isNull(getWhereClause())) {
               initChildFieldValues();

               if (childFieldValues == null) {
                  return SKIP_BODY;
               }
            }
         }


To do this the method mapChildFieldValues() from Table class is used..

Hope that helps for the beginning.

Henner


Best point to start debugging for filter/query problems is the dbform tag,
method doStartTag(), somewhere around line 1507. This is named as part III:
         // *************************************************************
         //  Part III - fetching Data. This data is provided to all sub-
         //  elements of this form.
         // ************* 

>From there the searchFields of the form are filled from
initSearchFieldValues().

The filter stuff is done earlier here:

         if (!Util.isNull(getSqlFilter())
                  && !Util.isNull(requestSqlFilterString)) {
            sqlFilterString = " ( " + requestSqlFilterString + " ) AND ( "
               + getSqlFilter() + " ) ";
         } else if (!Util.isNull(getSqlFilter())) {
            sqlFilterString = getSqlFilter();
         } else if (!Util.isNull(requestSqlFilterString)) {
            sqlFilterString = requestSqlFilterString;
         }

         logCat.debug("filter to apply : " + sqlFilterString);

         if (!Util.isNull(requestSqlFilterString)) {
            sqlFilterParams = DbFilterTag.getSqlFilterParams(request,
                  this.getTable().getId());
         }


Parent child filters are build much earlier in part II:

            // If whereClause is not supplied by developer
            // determine the value(s) of the linked field(s)
            if (Util.isNull(getWhereClause())) {
               initChildFieldValues();

               if (childFieldValues == null) {
                  return SKIP_BODY;
               }
            }
         }


To do this the method mapChildFieldValues() from Table class is used..

Hope that helps for the beginning.

Henner





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
DbForms Mailing List

http://www.wap-force.net/dbforms

Reply via email to