-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Improvements to clarify type using TypedParameterValue
#2461
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
Conversation
- For Hibernate provider, create `HibernateJpaParametersParameterAccessor` not `JpaParametersParameterAccessor` - Create `TypedParameterValue` by fetching parameter type from `HibernateJpaParametersParameterAccessor`
Thanks for your work, that's merged. |
There is a problem with this implementation. When EntityManager parameter in constructor is proxy created by SharedEntityManagerCreator, em.unwrap(Session.class) may (or will?) throw IllegalStateException with message "No transactional EntityManager available". Attached is small change that can fix that problem. |
Properly handle null values with like or contains. Null values are wrapped with a special handler when interacting with Hibernate. However, this becomes an issue for queries when LIKE or CONTAINS are applied. In this situation, the null needs to be condensed into an empty string and any wildcards can then be applied with expected results. Closes #2548, #2570. Supercedes: #2585. Related: #2461, #2544#
Null values are wrapped with a special handler when interacting with Hibernate. However, this becomes an issue for queries when LIKE or CONTAINS are applied. In this situation, the null needs to be condensed into an empty string and any wildcards can then be applied with expected results. Closes #2548, #2570. Supercedes: #2585. Related: #2461, #2544#
Null values are wrapped with a special handler when interacting with Hibernate. However, this becomes an issue for queries when LIKE or CONTAINS are applied. In this situation, the null needs to be condensed into an empty string and any wildcards can then be applied with expected results. Closes #2548, #2570. Supercedes: #2585. Related: #2461, #2544#
Null values are wrapped with a special handler when interacting with Hibernate. However, this becomes an issue for queries when LIKE or CONTAINS are applied. In this situation, the null needs to be condensed into an empty string and any wildcards can then be applied with expected results. Closes #2548, #2570. Supercedes: #2585. Related: #2461, #2544#
@cigaly Please check out the snapshots to see if your issue still persists. If so, please open a new ticket. |
Null values are wrapped with a special handler when interacting with Hibernate. However, this becomes an issue for queries when LIKE or CONTAINS are applied. In this situation, the null needs to be condensed into an empty string and any wildcards can then be applied with expected results. Closes #2548, #2570. Supercedes: #2585. Related: #2461, #2544#
HibernateJpaParametersParameterAccessor
notJpaParametersParameterAccessor
TypedParameterValue
by fetching parameter type fromHibernateJpaParametersParameterAccessor
Close #2370