Internal Website Search

we defined a composite index for class Action: @ Index (name="ssst",members={"startDate","state","subType","type"}) and an index for the OneToMany @OneToMany(fetch=FetchType.LAZY) @ Index public List ... and a.startDate ?1)) the composite index is not used, query plan:  Step 1: Process Action

" If many of the values in the field are the same, the index might not significantly speed up queries." "An index on the gender column likely would  not  help because there's no value in an index on a low cardinality column. Meaning, there's not enough variety in the values

(with and without String indexing ).  Is there some sort of tuning we can do to have both fast queries and not soak up all the memory on the server?   Thanks, CVTSC cvtsc Dev Team Using indexes should not make that difference. When indexes become available different query plans may be used to execute queries

Hi, I am trying to create some index in a DB - but I get an exception when i try to commit. Exception in thread "main" [ObjectDB 2.6.0_01] javax.persistence.PersistenceException Invalid index path ... (EMImpl.java:958)   Here is how the class of the persisted object looks like @Entity @ Index

indexed data). It is unclear yet how exactly this happened. support Support Apparently we found the bug, which affects indexes on pure Date fields (i.e. date with no time). ObjectDB converts pure ... .getOffset method changes. It could be any date, but the index will become corrupted

Is there a way to add single member index on members of a object member which is not configured ... = FetchType.LAZY) private List stores; // Setter/Getter } So I wanted to add index on Customer for merchant ... ; @Entity @Indices({ @ Index (members={"merchant.name"}), @ Index (members={"stores.name

Hi we have found that applying indexes on an existing table erases the data. Are we doing ... defined indexes . In earlier versions new indexes had no effect until the database was rebuilt using the Doctor. What ObjectDB version are you using? Because automatic activation of new indexes is a new

a problem with indexing . An index on a String field is required to give good performance but if I add the @ Index annotation to the field I eventually end up with an ObjectDB internal exception.  This is reproducible, as is the program running to completion (slowly) if I remove the @ Index

a performance problem using two indexes .  An entity I'm querying has two indexed fields ... == :objectReference order by id desc when an index is defined on the reference field should use that index ... where receiver == :r order by id desc Query Plan Description ====================== [Step 1] Scan index com

When populating a large database with objects that have indexed fields takes very much longer than populating the database with those objects if the index definitions are removed.  Is it possible to indicate in some way that for a particular use of the database indexes are to be ignored

Hello, I have composite index , and it was working fine, but now I need to add more features to the software and I need to throw more indexes in there. I wanted to know what's the best way to do this. 1. Have some admin tool CREATE INDEX ..... ON a.b or 2. add more @ Index to the object entities. in

Is it safe to add indexes on an existing entity class? Thanks. lo Hoel Safe, but to enable the new index you will have to rebuild it , currently using the Doctor. Before running the Doctor make sure that the index is registered in the database by opening the database when it has access to the new

Hello, we introduced a new index upon a String field Order.typeName, added to package.jdo as After starting our app with the new index on one database we got the following exception: 2019-02-01 04 ... and back then we could not get the new index working at all. jakab Gergely Jakab Thank

= -1"), } ) @Indices( { @javax.jdo.annotations. Index (members = {"id","pwd","access"}) } ) public ... , id2) : : so actually the id field is included in the index , and queries on pwd , access and id can be executed by using the index only with no need to access the data.  Adding a primary key field

index . This is the original code: @Entity public class ObjectDbEntity implements DataItemProvider ... ; private Value value = null; and I just want my key to be indexed on my db, just like this: @Entity ... ;   @ Index     private Key key = null;     private Value value

Hi! I have a project which has all entities as JPA entities. I would like to make use of indexing ... : will adding JDO @ Index in a JPA entity have any effect or I have to switch that entity to JDO? Question2 ... the JDO annotation with JPA without any additional change. If you add an index to an existing

Is there a way to create an Index with @ Index on the key of a map? wua Andreas Wurm Indexes on map keys as well as queries on map keys are currently not supported. But as a workaround you can use ... javax.jdo.annotations. Index ; import javax.persistence.*; public class T1255 {     public

Do the following annotations @OneToMany @ManyToOne @ManyToMany @OneToOne imply @ Index   ... ) should apply @Unique on the @One side. But ObjectDB doesn't apply these indexes automatically, because of their overhead (which most users are not aware of). You should use the @ Index or  @Unique annotations explicitly to set indexes . support Support

Hi, is there a way to put an Index on the values from an Map? For example, if I have a Map like ... = mmsContainer.values();   Thanks for you help   wua Andreas Wurm Indexes are used only in queries, and cannot accelerate other application code. You can define an index on a map value

that can be modified by a paticular user, since I will do this query often I would like to index it.  How would I tell ObjectDB to make an index and then use it in a query? I have yet to deploy this entity so I ... Herman You can define an index on a collection field as explained in the manual , and the index

to pick up the new schema and now none of the indexes work, except the @Id. I can query by any field that is not indexed on the existing Object but as soon as I try and query against a field that was indexed I get no results. Tried 2.4.2 and 2.4.2_02 with same results. bensteele Ben Steele Adding

seem to have specific documentation for this. Your documentation for JDO annotation @ Index mentions that it corresponds to the XML element which is one way to specify indexes in XML metadata. But there is another way which is to specify an indexed attribute on the field element, like or indexed ="true". It doesn't

Hi, Is there a way to "Rebuild Class Indexes " from the command line? I have just added a new index ... an index currently requires running the ObjectDB Doctor , which is run from the command line. ObjectDB 1 ... implemented in ObjectDB 2.x. Update: Starting ObjectDB 2.6.6 new indexes are automatically built and activated in the background . support Support

I have a question about partial indexing . For example, a field of String type ttt, will be distinguished by the first 5 characters, then I can make a index of substr(ttt,1,5) in MySQL. With ObjectDB ... only indexing of complete fields (single field or multiple fields). The obvious workaround

Hello, Is there a simple way to check if indexes specified in entities are well taken into account ... of indexes : When you execute a query in the Explorer in the log pane. In the log file if you enable query ... in log is not immediate. Well, how can i check index existence so ? xirt Sylvain The log

How do you do case insensitive indexes ? I have search the Forum and tutorials and have not found any info related to this.   Thanks, -- Nathan Modrzewski nmodrzewski Nathan Modrzewski Case insensitive string indexes are currently not supported. If you cannot use lowercase only (or uppercase

annotations: @ Index (unique="true") @Column(nullable=false,unique=true) the search no longer works. I ... demonstrates that ESCAPE in LIKE was ignored when using an index . Build 2.3.7_11 fixes this bug. Thank you for your report. support Support

Hello ObjectDB Team I might have read the solution to this issue some times before, but I could not find an answer now. So sorry for bothering you. I want do add an @ Index annotation to a member of an existing Entity. This changes affects also existing databases. Is there any best practice

Composite index support collection

on it.  See indexing errors reported. Run ObjectDB 2.7.1 on same .odb and you will not see indexing ... ; repaired.odb will still show indexing errors when ObjectDB 2.7.2 (or later) Doctor is run on the "repaired" database. Automatic index rebuilding (" ") does not correct the database. So, in summary, I

an existing one and I get 0 results when trying to query by an existing index (that still exists) and the below errors in the logs. I can query the object fine by non- indexed fields and by the @Id.   [2012-08-19 19:42:25 #74 store] *** Attempt to remove a non existing index entry: [2012-08-19 19:42

; private long   index ;     private String role; } @ Index (members = {"refs.role", "refs. index "}) @Entity public class ChangeSet {     @ElementCollection    ... .objectdb.com/database/support/636. I think index changes should never cause the application to stop

When a new index is added to an existing entity classes that already has instances in the database ... data. The Index Rebuilder tool will enable rebuilding indexes , synchronizing their data ... , in which such new indexes will be enabled. support Support Version 2.6.6 introduces a built in

an index that does not allow duplicate keys. An index on a collection or array (including byte ... also that an index on a collection or array will not be useful in queries that compare the entire array or collection ... , e.g. using a JOIN query. This is because every element is indexed as a separate index entry

userName is not synchronized with the index on that field. It is unclear how this happened ... the index by running the Doctor in repair mode: java com.objectdb.Doctor error.odb error2.odb ... when an object is indexed . We were aware to issues that are caused by schema changes against a running

"is not null"-queries are not working correctly for indexed fields. Following SSCCE creates 1000 entities. A null value is assigned to an indexed field for every second entity. When doing count ... . Index ; import javax.persistence.Entity; import javax.persistence.EntityManager; import javax

I would like to request support for case insensitive string indexes . Case-insensitive search is a very common requirement and adding a separate field for every indexed field is a pain. Regards, Natalia.   natmaclin Natalia Levine

The ability of ObjectDB to index collections, including collections of strings, can be very useful in text indexing and search. By splitting document text into words and keeping these words in a List persistent field, documents that contain specific words can be retrieved easily and efficiently

filter like this is used: ":ids.contains(originalId)" originalId is an indexed String field

Please check the attached database file. When running the Doctor, I get   Global Value Errors ------------------- [1] Unexpected last index ID: -119 (expected -116) Page Content Errors ------------------- [1] Page #9 entry 0 has unexpected object format [2] Page #9 entry 0 (key 'bjjl') has 75

. Since: JPA 1.0 Index [] indexes default {} (Optional) Indexes for the table. These are only used if table generation is in effect. Note that it is not necessary to specify an index for a primary key, as the primary key index will be created automatically. Since: JPA 2.1 int initialValue default 0

to the default catalog. Since: JPA 1.0 Index [] indexes default {} (Optional) Indexes for the table. These are only used if table generation is in effect. Note that it is not necessary to specify an index for a primary key, as the primary key index will be created automatically. Since: JPA 2.1 String

will apply. Since: JPA 2.1 Index [] indexes default {} (Optional) Indexes for the table

default foreign key strategy will apply. Since: JPA 2.1 Index [] indexes default {} (Optional) Indexes

either location, the persistence provider's default foreign key strategy will apply. Since: JPA 2.1 Index [] indexes default {} (Optional) Indexes for the table. These are only used if table generation is in

index () Create an expression that corresponds to the index of the object in the referenced association ... the index Since: JPA 2.0 ListJoin on ( Expression  restriction) Modify the join to restrict

associated with this join. Specify "true" or "false". Since: JDO 2.1 String index default "" The name of the index to generate. Since: JDO 2.1 String indexed default "" Whether the value column(s) should be indexed . Since: JDO 2.1 String mappedBy default "" Name of a member in the key class

with this join. Specify "true" or "false". Since: JDO 2.1 String index default "" The name of the index to generate. Since: JDO 2.1 String indexed default "" Whether the value column(s) should be indexed

". Since: JDO 2.1 String index default "" The name of the index to generate. Since: JDO 2.1 String indexed default "" Whether the join column is indexed . Since: JDO 2.1 String outer default

String index default "" The name of the index to generate. Since: JDO 2.1 String indexed default "" Whether the value column(s) should be indexed . Since: JDO 2.1 String mappedBy default "" Name