About Index

release

2.6.8

... Fixed a  NullPointerExeption on new index building . Fixed a NullPointerExeption on flush ( ... using external classes. Fixed Doctor's index rebuilding to use NULL values for missing values of new fields. ...

 
release

2.6.9

... Fixed a  NullPointerExeption on new index building . Fixed a NullPointerExeption on flush ( ... using external classes. Fixed Doctor's index rebuilding to use NULL values for missing values of new fields. ...

 
api-jdo

Index.name

Name of the index(Annotation Element of javax.jdo.annotations.Index)

 
forum_thread

Finding an object by its datetime

SearchBookingByTimeStamp() { Calendar btime = Calendar.getInstance(); btime.set(2012, 10, 11, 7, 30, 00); //This time is already inserted, trying to find it /* My Query */ TypedQuery<Booking> query = em.createQuery( "SELECT b FROM Booking b WHERE b.btime = :btime", Booking.class) .setParameter("btime", btime, TemporalType.TIMESTAMP); } @Entity public class Booking { @Temporal(TemporalType.TIMESTAMP) Calendar btime; }   ... Hi, I forgot the @Index beside @Temporal(TemporalType.TIMESTAMP) Calendar btime; It looks like this now in the entity class: @ Index @ Temporal ( TemporalType . TIMESTAMP ...

 
forum_thread

Problem with @UniqueConstraint

It seems there is a problem with @UniqueConstraint. Same annotations using hibernate works fine - an error will be thrown - duplicate name. ObjectDB - no exception will be thrown. with best regardsPeter... Until JPA defines Java object model level @Index / @Unique annotations (hopefully in next versions) - you will have to use JDO @Index javax.jdo.annotations.Index JDO annotation Annotation ...

 
forum_thread

Efficient query on EmbeddedId

Hi! I have an entity class with an @EmbeddedId (field1 int and field2 int). Based on the manual, I understand that making a query just on entity.id.field1 is efficient. Of course, making a query containing the whole EmbeddedId is the ideal case, and I use it, but I need more use cases. ... entity.id.field1 and entity.id.field2 form a composite index together, in the order in which they were declared. In this case, can I just declare an additional index on entitiy.id.field2 in the entity class as @Indices({@Index(members = ...

 
release

2.6.7

... using external classes. Fixed Doctor's index rebuilding to use NULL values for missing values of new fields. ... a bug in retrieving primary key fields in queries (on index merging). Fixed a bug in using a collection field index in ...

 
forum_thread

Possible issue with timestamps

Hi, If I query doing something like: select c from CDI c where c.creationDate > {ts '2012-03-29 11:00:00} and c.creationDate < {ts '2012-03-29 12:00:00'} the test fails. Its ONLY for 12:00:00. When I started digging I found that if I queried 00:00:00 to 00:25:00 and then did 12:00:00 to 12:25:00 I got IDENTICAL results. For some reason 12:00:00 is being treated the same as 00:00:00. All other hours seem to be fine. ... = id ; }   @ Index ( unique = "false" ) public String ... firstname ; }   @ Index ( unique = "false" ) public String ...

 
release

2.6.6

... using external classes. Fixed Doctor's index rebuilding to use NULL values for missing values of new fields. ... a bug in retrieving primary key fields in queries (on index merging). Fixed a bug in using a collection field index in ...

 
release

2.4.6

... a bug in retrieving primary key fields in queries (on index merging). Fixed a bug in using a collection field index in queries. Fixed query plan selection for queries with ...