 1 | I was only working on ObjectDB evaluation and did very careful install, library reassignment |
1 | and applications (e.g. one installation of ObjectDB server that serves many students in a University, each |
1 | I have being searching all around for how to do this but still no luck. I want objectdb to be able to listen in server mode to other connections from another machine where client is installed. I will like to have objectdb on machine A, while B,C, D can access the database in a using code like |
1 | How do you manage software release cycles with objectDB? For example we might have different installation of a given web application, and we might need to introduce new fields with default values or to change something in the database "structure". How can we apply the update script |
1 | to get something else back than an Unit object. I checked the DB two times and installed the copy generated by |
1 | referenced. Maybe you installed ObjectDB within Tomcat, and maybe I missed something in |
1 | above, although ObjectDB does not support in memory mode, you can use a RAM drive. i.e. install a RAM drive |
1 | second making a specific JDO manual Me too. I use ObjectDB as an esy-to-install and free example |
1 | generated any activation code and we built our application on this machine after installing |
1 | an existing Eclipse workspace, in which an older version of the driver was installed |
