5 | ObjectDB Explorer Exposes Username and PasswordHow can I prevent my embedded database's username and password from being exposed by ObjectDB Explorer? billdotnet Bill See url-history setting and the user and password attributes. support Support If I understand correctly, if someone were to remove the configuration file, the username |
5 | Deadlock problems solved - a suggestionThanks to the new logging capability, I have managed to solve all the deadlock problems, as they were a result of Objectdb encountering new classes in multi-threaded code. I have a suggestion that might be useful for other users - how about an Ant task that, given a database URL, performs |
5 | Occasionally slow requests in load testing-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log |
5 | Deploy ObjectDB in WildFly 10.jdbc.url" value="/tmp/objectdb/testdb.odb"/> <property name="javax.persistence.jdbc.user |
5 | Can't post on your forum parameter (e.g. ?x) to urls on our website? In addition, could you please check the cookies |
5 | Degrading performance overtime-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log |
5 | Convert embedded database to server a client-server connection url. support Support Thank you support for your answer. What are the pros |
5 | multiple connection using share folder of that computer. Access the database using a full url connection including host and port (see this manual |
1 | com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null() { } public long getId() { return id; } private @Index @Unique String url = ""; @Temporal(javax.persistence |
1 | ObjectDB 2.3.4 a page cache purge deadlock (issue #559). Fixed handling ;drop in client-server connection url. Fixed |
