 14 | Is there a way to encrypt the odb file so that if hackers somehow steal it they cannot access ... for a password for encrypted odb files. The way to keep an ObjectDB database encrypted is simply ... , directories or files, and an ObjectDB database is an ordinary file. If you are going to encrypt |
14 | .orm file, where X is a value passed to the PersistenceManagerFactory as the value of property "mapping ... for this type of file, though I can't see a mention of it in the manual. But I've tried creating one as ... our tests (that are part of every build), but in a package.jdo file rather than an orm file. Maybe |
14 | objectdb were not shutdown properly which in turn meant we had several odb$ files left behind. I ... below. No other process had a lock on the file, especially as the server had just been rebooted and the os allowed us to delete the files in question without any problem. In this case we weren't |
14 | a simple configuration file to determine available persistence units, and then bootstraps them using ... (again, obtained from the configuration file ). After the entity manager factory is obtained, the Metamodel is empty - none of the entities referenced in the mapping file are present in the Metamodel |
14 | old date files from database. And recalculate disk usage back ? Since an ObjectDB database is a single file you can simply check its size using the length() method. In embedded mode this should be simple. In client-server mode - you can retrieve the server file system root by:
File root = com |
14 | db odb file from version 1.x to 2.x, user is unable to open the odb files in the application which is having object db 1.x installed. Is there any way to read odb files from 1.x in object db 2.x ... that objectdb 1.x was having one row but after converting to objectdb 2.x, no row was present the odb file |
14 | Hello, we have questions about the file size of ObjectDB database on disk. Can you tell us something about how the deleting of entities affects the size of *.odb files on disk? -Will the released memory always used by new entities? -Will be the database file automatically reduced? We have created |
14 | "... />". Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly. What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)? Could you please verify that this setting is in the correct objectdb.conf file? As |
14 | of the DB files I got this error:
java -jar converter.jar ../old.odb ../new.odb
ObjectDB 1.0 -> 2.0 file conversion
Exception in thread "main" java.lang.RuntimeException: Internal Exception ... (Converter.java:26) Please advice how to solve this. I tried the conversion on another odb file which is 3G |
14 | -files:
file>META-INF/orm.xmlfile>
file>META-INF/ormreq.xmlfile ... .bl.impl.RequirementImpl9 Why the second mapping-file is ignored? The unit test has following result ... orm file is defined? If you do, please describe how exactly you invoke the Enhancer. Thank you very much. That works fine. Best regards, BTC-ES btc_es |