Details
-
Type:
Bug
-
Status: Verified
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.7
-
Fix Version/s: 10.8 [Tentative], 11.2
-
Component/s: Tests & Quizzes (Samigo)
-
Labels:None
-
11 status:Resolved
-
10 status:Resolved
-
Previous Issue Keys:SAM-3029
Description
It appears as though passing the java.util.Date in an Object array to Spring HibernateTemplate can cause some unexpected behavior as the type cannot be guessed correctly.
Spring has no way of knowing what Hibernate Types to use in HibernateQueries, so if you attempt to use any of the find* methods in the template, and you are using a Hibernate UserType/CustomType(s) as query parameters, Spring/Hibernate will not be able to guess the type correctly.
Gliffy Diagrams
Zeplin
Attachments
Issue Links
- relates to
-
SAK-34582 Auto-submit job depends on database server timezone instead of Java timezone
-
- CLOSED
-
-
SAK-35141 Auto submit job doesn't handle extended due dates
-
- Verified
-
-
SAK-35522 Non-Published assessment: Retract date should be set to null when saving with the "No, not after due date" option
-
- CLOSED
-