ObjectDB Database Search

haven't got an easily distributable test for replication , but It shouldn't take too long to write

part of the RDBMS-ObjectDB Replication  feature. You may subscribe to this feature request to increase

David Moshal Was able to replicate this error by running 2 clients against the same database server

- I lost a lot in the 'translation' of trying to replicate what was happening in my app

. Please try it. support Support As said, it still happens with criteria api and it is easy to replicate

replication and route READ operations to slave servers. Of course, some NoSQL solutions provide

applications - Performance is excellent!!) Thanks in Advance, Jana janu019 Janardhana ObjectDB replication

We are currently evaluating objectdb for our SaaS(multi-tenant) product. It is a data intensive health care product . We would like to know the horizontal scalability options available. arunjoy Arun Joy Horizontal scalability may be achieved by using replication . support Support Thanks

again it should be recovered automatically. In addition you may use replication and online backup

your application or a test case? support Support Hi, we are trying to replicate the problem and I will post

A to location B (unless it is replicated automatically) and then open the database in location B. support Support

again. Trianglehead Json Error This might not be related to replication but to cache in general

key. If you need to install ObjectDB also on developer / test machines, a replicated machine

by ObjectDB, as the supported replication is based on one master and multiple slaves

bug in opening tables for selected rows. Fixed a replication configuration error .

. Fixed a Doctor and Replication regression (Type session exceeds timeout). Removed  Conflicting modifiers  validation check and error message.

) which you can use to replicate the bug. We chose to use maven because of the static weaving step. JFK John

) at java.lang.Thread.run(Thread.java:680) Sorry but I've tried one hour to replicate it in a simple

Hi, When deleting an entity "Mitglied" - everything works fine. Trying to delete another one (in a separate transaction) always causes a NullPointer Exception in __odbGetNumMember line 1 of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in

due to disconnecting a replicated slave server. Fixed NOT NULL handling for basic (non relationship) references

it is very small with only 1 User in it. To replicate the issue you can do the following: SELECT u from

switching in master-slave replication . Fixed a bug in applying orphanRemoval=true by default on mapped by

.g. temporary files, recovery file) to other disks. using replication with multiple servers