-
Notifications
You must be signed in to change notification settings - Fork 356
MSSQL bit wrongly mapped to boolean value TRUE #908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Update: the conversion actually works but auto generated query does not. I thing that isTrue suffix should be automatically mapped to 0 or 1 in case of Mssql BIT type |
When implementing this we should double check that it works consistently with R2DBC |
The Any idea ? |
You can run all the integration tests and see if changes work for all databases: https://github.com/spring-projects/spring-data-jdbc#running-integration-tests |
All integration tests are green |
`IsTrue` and `IsFalse` queries no longer use a literal in the query, but a bind parameter. This allows Spring Data JDBC or the JDBC driver to convert the passed boolean value to whatever is required in the database. For Oracle converter where added to support storing and loading booleans as NUMBER(1,0) where 0 is false and everything else is true. Closes #908
`IsTrue` and `IsFalse` queries no longer use a literal in the query, but a bind parameter. This allows Spring Data JDBC or the JDBC driver to convert the passed boolean value to whatever is required in the database. For Oracle converter where added to support storing and loading booleans as NUMBER(1,0) where 0 is false and everything else is true. Closes #908 Original pull request #983
`IsTrue` and `IsFalse` queries no longer use a literal in the query, but a bind parameter. This allows Spring Data JDBC or the JDBC driver to convert the passed boolean value to whatever is required in the database. For Oracle converter where added to support storing and loading booleans as NUMBER(1,0) where 0 is false and everything else is true. Closes #908 Original pull request #983
Hi, I have this entity:
with this dao:
Optional<MasterSeller> findBySellerNameAndSellerCodeAndActiveIsTrue(String sellerName, String sellerCode);
Custom conversions do not work for me.
Exception is:
The text was updated successfully, but these errors were encountered: