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
In my opinion the methods WhereTrue|WhereFalse don't make any sense and must be removed from SQLKata because Oracle users can use anything in regarding the boolean type ('Y'/'N', 1/0, '1'/'0', 'True'/'False'). So SQLKata cannot predictate which type needs to be used in query. Or there must be some additional setting on the Oracle Compiler which each developer can amend in case of difference.
In my case I use NUMBER(1) type to use oracle column as a boolean. NHibernate has no issues with that column type having on the entity side bool type on the property passing 1 or 0 in the following query .Where("is_enabled", true).
Oracle: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
SQLKata: 2.3.3
.Net Core 3.1
C#:
Compiled SQL Query:
Please note the
usr.is_deleted = false AND usr.is_enabled = true
is wrong, instead it must beusr.is_deleted = 0 AND usr.is_enabled = 1
.Error:
However if I change as follows:
the error disappears.
The text was updated successfully, but these errors were encountered: