Uh oh!
There was an error while loading. Please reload this page.
Fix Internal Server Error When Filtering by String Column but the value can be interpreted as another type - #36
Conversation
… column whose data type is not a string.
| response.headOption.isEmpty must be(true) | ||
| } | ||
| "don't fail when the column is citext or similar, but the value can be interpreted as Int." in withApiClient { |
There was a problem hiding this comment.
When the value is CITEXT we should interpret it as string, any reason to interpret it as int?
There was a problem hiding this comment.
Before, if the value was "123", it was assumed that the value was an Int, and the same for the column type. This caused an internal server error because it compared a citext with an Int.
Same for the others comments
There was a problem hiding this comment.
From my point of view, the input argument must be handled like the type derived from the database instead of guessing its format.
There was a problem hiding this comment.
Yes, the changes in this pull request consider both the column type and the value to avoid this.
| email must be(emailValue) | ||
| } | ||
| "don't fail when the column is citext or similar, but the value can be interpreted as Decimal." in withApiClient { |
| email must be(emailValue) | ||
| } | ||
| "don't fail when the column is citext or similar, but the value can be interpreted as Date." in withApiClient { |
| email must be(emailValue) | ||
| } | ||
| "don't fail when the column is citext or similar, but the value can be interpreted as UUID." in withApiClient { |
Fixed an Internal Server Error, Caused when attempting to filter by a column is citext or similar, but the value can be interpreted as another type.