Menu ▾ ▴

#346 Index vectors may not be used in 'matop' mode

v1.1.x
fixed
Erik Hänel
critical (96)
v1.1.1
Bug Fix
2018-11-12
2018-06-04
Erik Hänel
No

In the matop mode, one cannot use an index vector to select specific data.

Analysis:
The reason for this misbehavior is that the indices of the tables are read after the matrix function evaluations are processed. The results are not considered in the calculation of the indices. A possible solution would be to add a wrapper around the getIndices() function, which will try to evaluate possible returned matrices first.

Implementation:
The fix was implemented as proposed by the analysis. Implementation tests were passed successfully.

Documentation:
Fix was documented in the changes log. Further documentation not needed.

Tests:
This fix was added to the automatic SW tests. The detected deviation was resolved in [r415].

Related

Commit: [r415]

Discussion

  • Erik Hänel

    Erik Hänel - 2018-06-10
    • status: open --> accepted
     

  • Erik Hänel

    Erik Hänel - 2018-06-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1,9 @@
 In the `matop` mode, one cannot use an index vector to select specific data.
+
+**Analysis:**
+
+**Implementation:**
+
+**Documentation:**
+
+**Tests:**
    • status: accepted --> analyzing
     

  • Erik Hänel

    Erik Hänel - 2018-06-28
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,6 +1,7 @@
 In the `matop` mode, one cannot use an index vector to select specific data.

 **Analysis:**
+The reason for this misbehavior is that the indices of the tables are read after the matrix function evaluations are processed. The results are not considered in the calculation of the indices. A possible solution would be to add a wrapper around the `getIndices()` function, which will try to evaluate possible returned matrices first.

 **Implementation:**
    • status: analyzing --> implementing
     

  • Erik Hänel

    Erik Hänel - 2018-06-29
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -4,7 +4,9 @@
 The reason for this misbehavior is that the indices of the tables are read after the matrix function evaluations are processed. The results are not considered in the calculation of the indices. A possible solution would be to add a wrapper around the `getIndices()` function, which will try to evaluate possible returned matrices first.

 **Implementation:**
+The fix was implemented as proposed by the analysis. Implementation tests were passed successfully.

 **Documentation:**
+Fix was documented in the changes log. Further documentation not needed.

 **Tests:**
    • status: implementing --> testing
     

  • Erik Hänel

    Erik Hänel - 2018-11-12
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -10,3 +10,4 @@
 Fix was documented in the changes log. Further documentation not needed.

 **Tests:**
+This fix was added to the automatic SW tests. The detected deviation was resolved in [r415].
    • status: testing --> fixed
     

    Related

    Commit: [r415]

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB