London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
Allow default values on all non-nullable fields
I agree with you but don't hold your breath, I doubt it will come anytime soon.
Allowing nulls is my recommendation, we have run into some rather nasty issues with non-null fields in the past as episerver sometimes creates objects without setting any custom meta fields and you will get an unhandled database exception when it is saved.
Jan 05, 2018 15:04
This thread is locked and should be used for reference only.
For some reason I am able to set a default value for non-nullable fields on the cls_Address table, but not for OrderGroupAddressEx. I would think that allowing the ability to set non-nullable fields would require the ability to set default values because otherwise it will throw a database error when trying to create a non-nullable field without a default value for tables that already have records. This is seriously limiting my ability to use Epi and maintain normal best practices when it comes to data-modeling.
Please include this feature as soon as possible.