Sunday, February 05, 2012
Support » Support Forum
Register Login
HomeWhat is NDO?- Executive Overview- NDO for DevelopersHow NDO Works- Persistent Classes- Mapping- Queries- Reverse Engineering- Inheritance, Polymorphism- Distributed ApplicationsLicensingSupport- Support Forum- FAQ- Solutions- Downloads- E-Mail Support- Tutorial VideosOnline ShopContact
Welcome to the NDO support forum!
Please register/login at the site if you want to post a thread. We sometimes copy support mails of common interest to the forum. They appear with anonymous sender. Please post your messages in English language if possible. You can do your posts also in German, we will translate your post and our answer so that all users of the forum can read your posts. The forum software requires that javascript is enabled. Please do not insert licence information or licence keys in forum posts. If you know a good answer to a post of another user, feel free to reply! The forum is monitored. We reserve the right to remove posts we consider not to be useful for other forum users.
Hi,
When adding new persistent classes or updating fields in existing classes how do I avoid rebuilding the existing database? In a production environment you would not want to delete data just because new tables are added.
Is it possible just to update the database schema from the “object model”?
It seems like the only option available is to call BuildDatabase on the PersistenceManager.
have a look at the <assemblyname>.ndodiff.x.y.sql files. These contain difference scripts. The x.y will be replaced by the schema version string, you enter in the NDO configuration dialog. That way you can produce an own difference script for each version of your software.
Note, that difference scripts have some limitations. There is no way for NDO to detect the renaming of classes and fields. In this situations you might have to edit the differece scripts by hand.
Best Regards:Mirko