You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assert.AreEqual(12345,data.ColumnBigInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
2220
2220
}
2221
2221
2222
2222
#endregion
@@ -2249,7 +2249,7 @@ public void TestSqlConnectionInsertAndQueryConversionFromDoubleToInt()
Assert.AreEqual(12345,data.ColumnInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
2253
2253
}
2254
2254
2255
2255
#endregion
@@ -2282,7 +2282,7 @@ public void TestSqlConnectionInsertAndQueryConversionFromDoubleToSmallInt()
Assert.AreEqual(12345,data.ColumnInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
2286
2286
}
2287
2287
2288
2288
#endregion
@@ -2480,7 +2480,7 @@ public void TestSqlConnectionInsertAndQueryConversionFromFloatToBigInt()
Assert.AreEqual(12345,data.ColumnBigInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
2484
2484
}
2485
2485
2486
2486
#endregion
@@ -2513,7 +2513,7 @@ public void TestSqlConnectionInsertAndQueryConversionFromFloatToInt()
Assert.AreEqual(12345,data.ColumnInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
2517
2517
}
2518
2518
2519
2519
#endregion
@@ -2546,7 +2546,7 @@ public void TestSqlConnectionInsertAndQueryConversionFromFloatToSmallInt()
Assert.AreEqual(12345,data.ColumnInt);// Legacy RepoDB indirectly used bankers rounding for this conversion, thus the current expected value is 12345 instead of the old 12346.
// If any of the fields is of type SqlVector<float>, we need to check the actual subtype of the vector, as SQL Server supports both float and real vectors.
171
+
// We can't just always query vector_base_type as that column is SqlServer 2025+
// If any of the fields is of type SqlVector<float>, we need to check the actual subtype of the vector, as SQL Server supports both float and real vectors.
249
+
// We can't just always query vector_base_type as that column is SqlServer 2025+
0 commit comments