 2 | .class); Hi! Thanks for the fast response - fast JPA impl and fast support! You are right, the first |
2 | even load at all. Sometimes it happens to load fast, but most of the time it's slow or very slow ... connection is blazing fast. Update: today it works pretty fast, but I can't log in using Chrome |
2 | fast, but when I also query using the other key, queries can take minutes. Looking at the database ... on the reference field should use that index and avoid a full scan. Does it run fast if the ORDER BY ... milliseconds. If ORDER BY is removed, the queries run very fast The second query is slow |
2 | initialization operation are required. But when repeating these operations they are very fast. Usually ... , and that is very fast. Thank you very much for you reply. The problem is that in my software |
2 | In my application I have an entity with few transient Collection fields, these are constantly updateing very fast and access to those fields is needs to be fast too, thus I dont persist them (also this information is temporary and doesent need to be kept). I suppose that entity modified is the same |
2 | that it would provide fast lookup, and the bookmark name I use is in fact simply the object primary key (a String ... of the primary key - it shows a "k" by the field in Object explorer. So, can I get fast primary key lookup in |
2 | Hi, does anyone have experience with database with more than billion records (ie. more than 1000 million records) in one table. What is the limit of ObjectDB and is the database still fast ... includes 2,000,000,000 instances of a simple entity class. ObjectDB is still fast, but obviously slower |
2 | .) Pseudocode for the fast and the slow solution FAST:
for (i = 0; i <100; i |
2 | query, with very fast execution time. Similarly to get MAX/MIN values:
SELECT MAX(m.id) FROM ... is indexed these queries also should be executed very fast. Thanks, it is much better now. FYI |
2 | mode. After fixing the index in that database (by running the Doctor) the query runs fast. Thanks ... indexed in objectdb 1.x, then how the query is very fast when i am using object db 1.x |