DataTable.Compute throws exception on "true NOT= false"
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
Research direction
Start with DataTable.Compute and the ExpressionParser.BuildExpression path shown in the stack trace, comparing how boolean equality and NOT expressions are parsed. Reproduce the failing expression and verify that it returns true without throwing, while the similar expressions and workaround continue to pass.
Written by the indexing model from the issue text.
Description
Description
DataTable.Compute() throws a System.IndexOutOfRangeException on a simple expression: "true NOT= false".
Reproduction Steps
using System.Data;
new DataTable().Compute("true NOT= false", null);
Expected behavior
I would expect DataTable.Compute() to execute successfully and return true.
Similar expressions are evaluated successfully by DataTable.Compute().
using System.Data;
using System.Diagnostics;
Debug.Assert((bool)new DataTable().Compute("1 NOT= 2", null) == true); // passes
Debug.Assert((bool)new DataTable().Compute("true = false", null) == false); // passes
Debug.Assert((bool)new DataTable().Compute("true NOT= false", null) == true); // exception thrown
Actual behavior
A System.IndexOutOfRangeException is thrown. Stack trace:
Unhandled exception. System.IndexOutOfRangeException: Index was outside the bounds of the array.
at System.Data.ExpressionParser.BuildExpression(Int32 pri)
at System.Data.ExpressionParser.Parse()
at System.Data.DataExpression..ctor(DataTable table, String expression, Type type)
at System.Data.DataTable.Compute(String expression, String filter)
at Program.Main()
Command terminated by signal 6
Regression?
No response
Known Workarounds
Can work around the problem by reformulating the expression:
using System.Data;
using System.Diagnostics;
Debug.Assert((bool)new DataTable().Compute("NOT(true = false)", null) == true); // passes
Configuration
No response
Other information
No response
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·