You’re offline. This is a read only version of the page.
Announcements
250
The on-prem SQL Server has a table with a column of type BIT to store true/false values. These values are stored as integers 0 or 1 in the DB engine. When you use the Execute SQL Query V2 with an ODATA filter against this type of columns (fields), everyone and his dog's first instinct would be to write something like this (when selecting for true values):
Share
Reportboolean_field eq true or boolean_field eq 1
since this is the only sane thing that comes and should come to mind. But Nooooo! Leave it to Microsoft to find a way to force users into Gotham's lunatic asylum because insanity seems to be the preferred state of mind!
Therefore our overlords in Redmond decided in their infinite wisdom that the following is what should come to mind naturally:
boolean_field ne 0, for ex to select all true values
This does indeed work as expected. But why, oh why Microsoft!?
Then again, perhaps it is just a bug... which seems to have been lurking since August 2020--can you believe this?! 2+ years and counting. Honestly, this is worthy of
All responses (
Answers (
