Home » Search

About manual

141-150 of 200Refresh
Forum
1

config file for embedded database

side and the server side). It is explained on this manual page. dmoshal
Forum
1

Connecting to a remote objectdb server

root directory. See this manual page.   I've tried your suggestion already. Isn't that objectdb
Forum
1

Database server with an application

Hi, I read the database server section of the manual - and it looks like it is not possible to connect to a Database embedded with an application from another application - is that correct? The way to go is to have the DB server running by itself and then the 2 other applications connecting
Forum
1

Delete object from collection versus delete from JPQL

between memory and database objects. See these manual pages for more details: DELETE queries UPDATE
Forum
1

Does aggregate function "greatest" work on entity objects?

in queries. See the list of Comparable Data Types in the manual. galandor
Forum
1

Drop JDO support

In my opinion JDO is a legacy/deprecated technology. You should remove JDO support in favour of JPA. I think this would make ObjectDB to grow faster. ObjectDB already supports JPA and this is its main API (e.g. the manual focuses on JPA). We have no reason to drop JDO, as there are still ObjectDB users that use it. tuille
Forum
1

Drop the entire database, Change the schema

). But your solution of adding support of drop to the odb extension is fine. See the manual for more information on database urls and this configuration. JFK dmoshal
Forum
1

Duplicate Entity class names causes Exception in Query

the manual. But of course, ObjectDB should not throw a NullPointerException in this case. I will try
Forum
1

Eclipse - Maven - Dependencies not getting automatically reflected

(http://repo.maven.apache.org/maven2). In case, if I manually put required artifcatID in pom.xml
Forum
1

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. My question