 301 | Date and time expressions may appear in JPQL queries: as date and time literals - e.g. {d '2011-12-31'}, {t '23:59:59'}. as parameters - when date and time values are assigned as arguments. as path expressions - in navigation to persistent date and time fields. as results of predefined JPQL current |
83 | Static Field javax.jdo.Constants String PMF_ATTRIBUTE_SERVER_TIME_ZONE_ID The name of the persistence manager factory element's "server-time-zone-id" attribute. Since: JDO 2.1 |
83 | Enum Constant javax.persistence.TemporalType TIME Map as java.sql.Time Since: JPA 1.0 |
82 | Static Field javax.jdo.Constants String PROPERTY_SERVER_TIME_ZONE_ID Mapping "javax.jdo.option.ServerTimeZoneID" Since: JDO 2.1 |
82 | Enum Constant javax.jdo.annotations.VersionStrategy DATE_TIME Since: JDO 2.1 |
39 | ObjectDB support wrote elsewhere: ... you do not need the Enhancer agent, since you use build time ... to disable the enhancer agent ... Q: Does run time enhancer due to GlassFish/Payara do anything that would affect loaded compile-time enhanced entity classes (other than just logging, typically just info |
31 | , why? Result:
===========
find time @ 24.125000
getSons time @ 0.000000
1 : type:Nodes, sons:2
child : 2
child : 3
Iterator time @ 0.000000
find time @ 0.000000
getSons time @ 0.000000
2 : type:Nodes, sons:2
child : 4
child : 5
Iterator time @ 0.000000
find time @ 0.000000
getSons |
30 | ): We create a 1G DB file when the application starts for the fist time. The size of the DB file does not ... one time. The load never exceeds more than 5 transactions per 10 seconds. So far we know ... of October at 3am. We think this is significant as this is exactly the time when Madrid changed clocks |
29 | Hihi, I'm wondering if this is a bug. I have a simple entity with java.sql.Time field. On writing ... time. Currently there is no known bug that may cause this. Maybe it is related to your specific ... that also prints the default time zone (and with some fixes and adjustments to the posting instructions |
29 | only fields. The object and its date and time fields are the same as in the referenced thread. Except we are using ObjectDB 2.6.4_08, the system time zone is set to EST and both the OS and JVM are using the 2015g time zone data. While we cannot see a problem with date only fields (more testing |