Home » Search

About point

151-160 of 200Refresh
Forum
0

First query takes 4+ minutes to complete

on why this is happening and how we can avoid it will be very much appreciated. Our next test point is 500,000 record
Forum
0

Geospatial functions

Hi, is it possible to implement geospatial functions (e.g. calculating distance between too points given latitude/longitude) ?Normally you would calculate the distance like: double cx = Math.toRadians(fromLat); double cy = Math.toRadians(fromLon); double px = Math.toRadians(toLat); double py
Forum
0

Glassfish 4 JTA Data Source Support

missing a vital point or unnecessarily re-inventing something that exists already. Is there ObjectDB
Forum
0

Guestbook Tutorial (Eclipse/Glassfish)

. At some point, may be when restarting Glassfish or re-publishing the application, the database
Forum
0

Homepage and forum nearly inaccessible

Homepage and forum nearly inaccessible from France/Germany, takes minutes to react. I'm guessing that the cause of the page delays is already known, but as an additional data point I'm experiencing a 15 or so second delay here in Canada where  a second or two is normal for me. Due to severe
Forum
0

How the sort order (in queries) works for non english letters?

anyhow. Maybe some property one could set when creating a new ObjectDB datafile? This is a good point
Forum
0

How to configure where the ODB is stored?

Hi, The documentation is lacking in this respect. How do I configure where the ObjectDB database file is stored. I need to know where it is so I can inspect it with 'database explorer'. The docs say to set it to "$objectdb/db/points.odb" and that this defaults to "the installation directory
Forum
0

How to define Default Entity Listeners without persistence.xml and orm.xml

.createEntityManagerFactory("$objectdb/db/points.odb", config); EntityManager em = factory.createEntityManager
Forum
0

How to use JOIN FETCH?

selects problem, which isn't going to be acceptable from a performance point of view. A similar
Issue
0

Inefficient memory usage with very large transactions

When a large transaction is committed, ObjectDB increases some internal structures, i.e. allocates more memory, but from that point the structures remain big and the memory is not released even if all the next transactions are small. This problem was found during a heap analysis (see #9 in