Home » Search

About feature

111-120 of 200Refresh
Result
1

ObjectDB version 2.6.5

(feature request #1658). Fixed a bug in persisting dates (TemporalType.DATE) based on time close
Result
1

ObjectDB version 2.6.9

Version 2.6.9 Added support for integration with WebSphere / Liberty application server. Fixed deleting large transaction temporary files (in the experimental large transactions feature). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects
Issue
1

[Explorer] Executing Queries

The new Explorer of ObjectDB 2 supports retrieval of database objects by classes and navigation. Retrieval of database objects by executing queries visually should also be supported. This is one of the features that have been supported by the old Explorer of ObjectDB 1. It has been temporarily
Issue
1

[Explorer] Running Tools

The Explorer should support running ObjectDB tools (such as ObjectDB Server and ObjectDB Doctor) visually within the Explorer. This is one of the features that have been supported by the old Explorer of ObjectDB 1. It has been temporarily removed due to incompatibility with the new ObjectDB 2 code base.
Forum
1

A nested SELECT

by ObjectDB. See this list of JPA features that are not implemented yet by ObjectDB. Vladiator
Forum
1

Activation Issue

without Connection feature (which was implemented following your request two years ago). Build 2.5.7_04
Forum
1

auto-generated uuid fields

language itself supports it (java.util.UUID). This is currently not supported. Discussion was moved to a new feature request in the issue tracking. spiffy
Issue
1

Automatic Switch to Replicated Server Limitations

ObjectDB supports master-slave replication, with the ability to switch connections automatically to another server when a server goes down, by specifying a composite url. Currently this feature has the following limitations: The first server in the composite url has to be available when connecting
Issue
1

Best practice for history tracking

and feature requests and not for general discussion and questions. In addition, every post should discuss
Issue
1

Better OSGI Compability

(which is due the special osgi class loader strategies) Making ObjectDB more OSGI friendly is an important feature