-
Notifications
You must be signed in to change notification settings - Fork 383
Make D2 dates related functions SqlBuilder aware (DHIS-16705) #19380
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
Merged
luciano-fiandesio
merged 5 commits into
master
from
DHIS-16705_D2_DATE_EXPRESSIONS_SQLBUILDER
Dec 5, 2024
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
8ea488d
Make D2 dates related functions SqlBuilder aware (DHIS-16705)
luciano-fiandesio 0b49641
Merge branch 'master' into DHIS-16705_D2_DATE_EXPRESSIONS_SQLBUILDER
luciano-fiandesio ebb87e3
Fix unit tests
luciano-fiandesio e4cd6a5
Fix Sonar comments
luciano-fiandesio 053eab9
Fix Unit + Integration tests
luciano-fiandesio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
114 changes: 114 additions & 0 deletions
114
...ces/dhis-service-core/src/test/java/org/hisp/dhis/program/function/D2DaysBetweenTest.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,114 @@ | ||
| /* | ||
| * Copyright (c) 2004-2024, University of Oslo | ||
| * All rights reserved. | ||
| * | ||
| * Redistribution and use in source and binary forms, with or without | ||
| * modification, are permitted provided that the following conditions are met: | ||
| * Redistributions of source code must retain the above copyright notice, this | ||
| * list of conditions and the following disclaimer. | ||
| * | ||
| * Redistributions in binary form must reproduce the above copyright notice, | ||
| * this list of conditions and the following disclaimer in the documentation | ||
| * and/or other materials provided with the distribution. | ||
| * Neither the name of the HISP project nor the names of its contributors may | ||
| * be used to endorse or promote products derived from this software without | ||
| * specific prior written permission. | ||
| * | ||
| * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND | ||
| * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | ||
| * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE | ||
| * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR | ||
| * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES | ||
| * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; | ||
| * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON | ||
| * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | ||
| * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS | ||
| * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | ||
| */ | ||
| package org.hisp.dhis.program.function; | ||
|
|
||
| import static org.junit.jupiter.api.Assertions.*; | ||
| import static org.mockito.Mockito.when; | ||
|
|
||
| import org.hisp.dhis.db.sql.DorisSqlBuilder; | ||
| import org.hisp.dhis.db.sql.PostgreSqlBuilder; | ||
| import org.hisp.dhis.db.sql.SqlBuilder; | ||
| import org.hisp.dhis.parser.expression.CommonExpressionVisitor; | ||
| import org.junit.jupiter.api.BeforeEach; | ||
| import org.junit.jupiter.api.Nested; | ||
| import org.junit.jupiter.api.Test; | ||
| import org.junit.jupiter.api.extension.ExtendWith; | ||
| import org.mockito.Mock; | ||
| import org.mockito.junit.jupiter.MockitoExtension; | ||
|
|
||
| @ExtendWith({MockitoExtension.class}) | ||
| class D2DaysBetweenTest { | ||
|
|
||
| @Mock private CommonExpressionVisitor visitor; | ||
|
|
||
| @Nested | ||
| class PostgresTests { | ||
| private D2DaysBetween function; | ||
| private SqlBuilder sqlBuilder; | ||
|
|
||
| @BeforeEach | ||
| void setUp() { | ||
| function = new D2DaysBetween(); | ||
| sqlBuilder = new PostgreSqlBuilder(); | ||
| when(visitor.getSqlBuilder()).thenReturn(sqlBuilder); | ||
| } | ||
|
|
||
| @Test | ||
| void shouldGenerateSqlForLiteralDates() { | ||
| String startDate = "'2023-01-01'"; | ||
| String endDate = "'2023-01-02'"; | ||
|
|
||
| String result = (String) function.getSqlBetweenDates(startDate, endDate, visitor); | ||
|
|
||
| assertEquals("(cast('2023-01-02' as date) - cast('2023-01-01' as date))", result); | ||
| } | ||
|
|
||
| @Test | ||
| void shouldGenerateSqlForColumnReferences() { | ||
| String startDate = "enrollment_date"; | ||
| String endDate = "incident_date"; | ||
|
|
||
| String result = (String) function.getSqlBetweenDates(startDate, endDate, visitor); | ||
|
|
||
| assertEquals("(cast(incident_date as date) - cast(enrollment_date as date))", result); | ||
| } | ||
| } | ||
|
|
||
| @Nested | ||
| class DorisTests { | ||
| private D2DaysBetween function; | ||
| private SqlBuilder sqlBuilder; | ||
|
|
||
| @BeforeEach | ||
| void setUp() { | ||
| function = new D2DaysBetween(); | ||
| sqlBuilder = new DorisSqlBuilder("doris", "doris"); | ||
| when(visitor.getSqlBuilder()).thenReturn(sqlBuilder); | ||
| } | ||
|
|
||
| @Test | ||
| void shouldGenerateSqlForLiteralDates() { | ||
| String startDate = "'2023-01-01'"; | ||
| String endDate = "'2023-01-02'"; | ||
|
|
||
| String result = (String) function.getSqlBetweenDates(startDate, endDate, visitor); | ||
|
|
||
| assertEquals("DATEDIFF('2023-01-02', '2023-01-01')", result); | ||
| } | ||
|
|
||
| @Test | ||
| void shouldGenerateSqlForColumnReferences() { | ||
| String startDate = "enrollment_date"; | ||
| String endDate = "incident_date"; | ||
|
|
||
| String result = (String) function.getSqlBetweenDates(startDate, endDate, visitor); | ||
|
|
||
| assertEquals("DATEDIFF(incident_date, enrollment_date)", result); | ||
| } | ||
| } | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m curious — was there a particular reason we opted not to use dependency injection in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit of a long story, in reality this new ExpressionMapBuilder is no longer needed, because @jimgrace showed me a better/simpler way to access the SqlBuilder. But since it was there, I figured that we can keep the list of expressions encapsulated into its own class, and yes, this could use DoI. Not sure, shall I just get rid of
ExpressionMapBuilderaltogether?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's OK. In
DefaultExpressionServicethese maps are still generated in the service (for all the expression types that are not program indicators), so this is not consistent with that. But all this ANLR code will be ripped out when we transition to Jan B's new parser. (Did you know about that?) I'm OK with keeping it as a separate class or putting it back where it was.