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 Michael,
NDO supports Nullables:
[NDOPersistent]public class MyClass{ Nullable someValue; // will be persisted ...}
Having said that, I'd recommend not to use Nullables under normal circumstances, because you need a lot of unnecessary logic to test if a certain field is initialized. There are some rare cases where it makes sense to persist an "undefined" state and the Nullables are for these rare cases. In all other cases try to use define default values for your numeric fields.
Note that strings being null, DateTime.MinValue and Guid.Null are persisted as NULL by NDO and vice versa, so that you don't need Nullables for these datatypes.
Best Regards:Mirko