Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2968

Incorrect rewrite of not disjunctive criteria

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 5.1.0 GA
    • Fix Version/s: 5.2.0 ER1
    • Component/s: EDS
    • Labels:
      None
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use the conjunctive normal form of the condition, e.g. instead of "not((a or b) AND c)", use "(not(a) or not(c)) and (not(b) or not(c))"

      Show
      Use the conjunctive normal form of the condition, e.g. instead of "not((a or b) AND c)", use "(not(a) or not(c)) and (not(b) or not(c))"
    • Estimated Difficulty:
      Low
    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-2968

      The coding for "not disjunctive" conditional criteria was inaccurate. This has now been fixed so users can add these conditions and find that they will be interpreted accurately by the software.
      Show
      https://issues.jboss.org/browse/SOA-2968 The coding for "not disjunctive" conditional criteria was inaccurate. This has now been fixed so users can add these conditions and find that they will be interpreted accurately by the software.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      The rewrite of a condition such as "not((a or b) AND c)" with a,b,c predicates where c a is predicate that is negatable, such as col1 = 1. The result should have the negated form of col1 <> 1, but instead has col1 = 1. This is because the col1 = 1 predicate is repeated in the result, but not cloned and the rewriter modifies the same instance.

        Gliffy Diagrams

          Attachments

            Issue Links

            cloned from

            Bug - A problem which impairs or prevents the functions of the product. TEIID-1498 Incorrect rewrite of not disjunctive criteria

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed

              Activity

                People

                • Assignee:
                  van.halbert Van Halbert
                  Reporter:
                  shawkins Steven Hawkins
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: