We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version 3.2.2.
class NotConditionVisitor extends TypedSubtreeVisitor<NestedCondition> {
should be
class NotConditionVisitor extends TypedSubtreeVisitor<Not> {
https://github.com/spring-projects/spring-data-relational/blob/main/spring-data-relational/src/main/java/org/springframework/data/relational/core/sql/render/NotConditionVisitor.java#L30
Test to reproduce:
@Test public void broken() { // when Select selectFalse = Select.builder() .select(Expressions.just("*")) .from("test_table") .where(Conditions.just("true").not()) .build(); String renderSelectFalse = SqlRenderer.create().render(selectFalse); // then - SELECT * FROM test_table assertEquals("SELECT * FROM test_table WHERE NOT true", renderSelectFalse) }
To be honest, it feels super dangerous.
The text was updated successfully, but these errors were encountered:
Thanks for finding and reporting this.
You have a double not in your second test. Could you confirm that that is a mistake? Otherwise I don't understand the test.
not
where(Conditions.not(Conditions.nest(Conditions.just("true"))).not()) ^ ^
Sorry, something went wrong.
Oh, yes, second part of test is broken. but first one seems to be correct.
(updated issue by removing second test)
Fixed rendering of NOT condition.
9ab3567
Closes #1945
b930d57
66466e8
schauder
No branches or pull requests
Version 3.2.2.
should be
https://github.com/spring-projects/spring-data-relational/blob/main/spring-data-relational/src/main/java/org/springframework/data/relational/core/sql/render/NotConditionVisitor.java#L30
Test to reproduce:
To be honest, it feels super dangerous.
The text was updated successfully, but these errors were encountered: