Skip to content

Conversation

@MikeNeilson
Copy link
Contributor

Update Tomcat version.

Location levels could only be retrieved by exact data. Expected behavior
was most recent.

during #1086 the "exact" match flag was changed from true to false.
Change is behavior was not correctly caught due to all tests using the
exact dates and the endpoint itself not providing appropriate
description.

Description has been updated.

The virtual location level tests were modified to specify exact date. In
diagnosing the issue I've discovered that the order of these operations
is wrong:

https://github.com/HydrologicEngineeringCenter/cwms-database/blob/f2670f46de2f41b724ac9d516505fa9a37c50cfa/schema/src/cwms/cwms_level_pkg_body.sql#L612

Virtual location levels should still support "or nearest before
behavior" but at the least with match being false while providing the
exact date should return the level and it does not.

I've set the default behavior of exact match to False, knowing this will
break existing virtual location level behavior, however, that will be
corrected with a database procedure fix.

(cherry picked from commit b2dfea9)
@MikeNeilson
Copy link
Contributor Author

ah, wrong target branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants