Internal Website Search
11-20 of 200 resultsRefreshSchema Evolution Question must be restarted after a schema change. " It is unclear whether the client application with the upgraded schema must connect to ObjectDB before the restart or whether ObjectDB can be restarted while the client is down and then have the client with the upgraded schema connect. That is to say | |
How to enable and disable auto schema update? Hello, Can I enable and disable the auto schema update? In some cases if multiple ... ; Expected : Instate of updating the schema with old library db should throw some error and data ... schema upgrade: System.setProperty | |
Schema update: package, class and field Hello, how can it be specified in the schema, that an entity is moved ... > How should that be specified in the schema? I found in the manual only how a whole packet can be renamed: <schema> <package name="com | |
Complex Schema Upgrade not working Hello, We're trying to upgrade the DB-Schema. Simplied our source/original Schema/Class-Hierarchy looked like this: class contact.Contact ... > We've added the schema upgrade to the objectdb.conf: <schema | |
Schema-Update: Deactivation of automatic entity class removing and introduction of a new class remove in the schema config when we have made changes to DB schema for new versions. Our solution is that we create a seperate product (we call it ProfileMigration) for each new application to handle all database (schema ... the schema config (objectdb.config), that should be deleted. In the future | |
ObjectDB Object Database Features> Schema Evolution Fully schema">automatic schema evolution and type versioning. Class ... /schema">renaming types, fields and properties. | |
boolean field flips after schema update (in class) of another field to issue #2621, if this class had many previous schema evolution changes (you might have a longer history of schema changes in deployment databases than in your test databases). support Support I think the schema may changed 2-5 times during the last months  | |
Step 6: Set the Spring XML="windows-1252"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p" xmlns:context="http://www.springframework.org/schema/context" xmlns:mvc="http://www | |
Step 6: Set the Spring XML xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p" xmlns:context="http://www.springframework.org/schema/context" xmlns:mvc="http://www.springframework.org/schema | |
[ODB1] Chapter 3 - Persistent Classes;Automatic Schema Evolution Most of the changes to persistent classes do not affect ... . Changes to persistent fields (schema changes), however, do affect the database. New persistent objects are stored using the new schema (the new class structure), and old persistent instances |