ObjectDB Database Search
1-23 of 23 resultsJPA Persistable Types.util.Date , java.util.Calendar , java.sql.Date , java.sql.Time , java.sql. Timestamp , java.time ... - represents the time only ( for example, `23:59:59 `). java.sql. Timestamp - represents both date and time ... ( TemporalType . TIME ) java.util.Calendar time3; // Date and Time: java.sql. Timestamp dateAndTime1; @Temporal | |
Possible issue with timestampsPossible issue with timestamps | |
Date and Time in JPQL and Criteria Queries : Returns the current time as a java.sql.Time instance. CURRENT_ TIMESTAMP : Returns the current timestamp (date and time) as a java.sql. Timestamp instance. Extracting date parts JPA does not define | |
FROM clause (JPQL / Criteria API), CURRENT_TIME, CURRENT_ TIMESTAMP ,DELETE, DESC, DISTINCT, ELSE, EMPTY, END, ENTRY, ESCAPE, EXISTS, FALSE | |
JPA Attributes Annotations . An enumeration defining the SQL type mapping: DATE , TIME , or TIMESTAMP . For more details, see the Persistent Classes chapter in the ObjectDB manual. | |
Index Definition.util.Date , java.sql.Date , java.sql.Time , java.sql. Timestamp Any enum type A reference | |
General Performance Issues Illustrated with a Specific Method createdBy; @Temporal(javax.persistence.TemporalType. TIMESTAMP ) private Date createdAt; @Temporal(javax ... (javax.persistence.TemporalType. TIMESTAMP ) private Date lastEditeAt; /* Retire Reversal Properties ... .TemporalType. TIMESTAMP ) private Date retiredReversedAt; /* Retire Properties */ private boolean | |
LifeCycle Event with Embeddable classes = FetchType.EAGER) private List barList; @Temporal(TemporalType. TIMESTAMP ) private Timestamp modifyDate; @PrePersist @PreUpdate void onPreUpdate() { modifyDate = new Timestamp (System.currentTimeMillis()); }} @Embeddable public class Bar { @Temporal(TemporalType. TIMESTAMP ) private Timestamp modifyDate | |
query on calendar class; @Temporal(TemporalType. TIMESTAMP ) private Calendar start; I tested: Query query=em.createQuery ... a Calendar to a Date . Using Date or Timestamp as the field type instead of Calendar ... . Timestamp , java.util.Date with @Temporal(TemporalType.DATE), @Temporal(TemporalType.TIME | |
TemporalType injection with Calendar using JPA. TIMESTAMP When I use a java.util.Date as a field on this object there is no problem. However, if I ... ; private String periodType; @Temporal(TemporalType. TIMESTAMP ) public Calendar getBeginTime() { return ... (TemporalType. TIMESTAMP ) public Calendar getEndTime() { return endTime; } public void setEndTime | |
Database is locked when in use am using the JDO not JPA, and can you also please tell if i dont want the timestamp ... . support Support Thanks. How should i get rid of Timestamp directory ? I am going to use ... want all the odb files to be placed in "backup" directory not backup/[ timestamp ] directory | |
Migration problem class GenericEntity extends BaseEntity { @LastModifiedDate @Column(columnDefinition = " timestamp ... (columnDefinition = " timestamp default '2020-04-10 20:47:05.967394'", updatable = false) protected | |
Order in WHERE Clause affects behaviour on DATE/DATETIME columns Quick example: public class MyClass { @Column(name = "myText") String myText; @Temporal(TemporalType. TIMESTAMP ) @Column(name = "myDate") Date myDate; } Now, when querying the db with: Query q ... the query parameter as TemporalType. TIMESTAMP . But when I write following query: Query q = JPA.em | |
Error using query with MAX() function @Temporal(value = TemporalType. TIMESTAMP ) private Date changeDate; public int getId() { return id | |
JPQL query to get entities that does not have a child entity in their child entities; Timestamp   | |
Dates to GMT, so in the database all the date and timestamp values are GMT. When the value is retrieved | |
Unexpected COUNT Results; SELECT $1.id FROM Pa3DataKey $1 WHERE $1. timestamp | |
java.sql.Time field off by 30 minutes Hihi, I'm wondering if this is a bug. I have a simple entity with java.sql.Time field. On writing and readback, the field is found to be 30 minutes off. It is observed on objectdb explorer as well. Timestamp works perfectly fine. Ps. dont think its a UTC issue. My system is set at far off UTC | |
Performance in SELECT statement; private long timestamp ; @Embedded   | |
Date field Index is corrupted due to time change; @Basic(optional = false) @Temporal(TemporalType. TIMESTAMP | |
Queries are slow on a large database; private String sendingNodeId; private String receivingNodeId; private Date timeStamp ; private String | |
Best practice for history tracking We would like to add to records start and end timestamp fields. When end field is null, it indicates the last version of this item. Few questions: in terms of performance, what would be faster, having a single timestamp and looking for the top1 when ordered by time or the above solution, looking | |
NPE at com.objectdb.jpa.JpaQuery.getResultList.sql. Timestamp dateTime; } } support Support Unfortunately, I have not |