Commit b5a8561
Fix numeric UInt64.MaxValue test case to use runtime adjustment
Changed the InlineData for numeric literal (EnumU64)18446744073709551615 to initially expect {"Prop":-1} (matching MySQL's behavior) and enhanced the runtime adjustment logic to check the actual numeric value instead of just enum equality.
The fix:
1. Changed InlineData JSON expectation from {"Prop":18446744073709551615} to {"Prop":-1}
2. Updated condition from `value == EnumU64.Max` to `(ulong)value == 18446744073709551615`
3. This catches both EnumU64.Max and (EnumU64)18446744073709551615 representations
Now both test cases for UInt64.MaxValue (symbolic and numeric) properly adjust expectations for MariaDB at runtime, allowing all 7 test cases to pass on both MySQL and MariaDB.
Co-authored-by: renemadsen <[email protected]>1 parent 3be5714 commit b5a8561
File tree
1 file changed
+3
-2
lines changed- test/EFCore.MySql.FunctionalTests/Query
1 file changed
+3
-2
lines changedLines changed: 3 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
64 | | - | |
| 64 | + | |
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | 68 | | |
69 | | - | |
| 69 | + | |
| 70 | + | |
70 | 71 | | |
71 | 72 | | |
72 | 73 | | |
| |||
0 commit comments