Uploaded image for project: 're-motion'
  1. RM-3701

The query parser used by QueryProviderBase can now be replaced or decorated

    Details

    • Type: New Feature
    • Status: Closed (View workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 1.13.92
    • Components: Data.Linq
    • Labels:
      None
    • Sprint:

      Description

      Due to several refactorings in the re-linq front-end, the QueryParser normally used by the query provider can now be replaced by a custom implementation of the IQueryParser interface. This enables full control over the parsing process.

      Replace the query parser to implement post-processing of the QueryModel before it gets passed to the IQueryExecutor, to cache parsed queries, or in similar situations.

      To preprocess the parsed expression tree, light-weight transformations based on IExpressionTransformer<T> and ExpressionTransformerRegistry and custom tree processing steps (IExpressionTreeProcessingStep) are usually better-suited as they allow more fine-grained customization.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                fabian.schmied Fabian Schmied
                Reporter:
                fabian.schmied Fabian Schmied
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: