This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Jeremy, I had a column that was set to non nullable and had been using it that way. Then we wanted to change it to nullable as it is no longer required. When I updated the LS model, it did not change the Validate Presence to false and was returning an error. When I manually changed it to false, then everything was fine. Thought you might want to know about this. version 5.0.2309.0 Craig |
|
|
Thanks Craig, This is in fact intended behaviour, we dont update the validations based on a nullability change as its valid to have the column nullable but you may still want to enforce a presence validation so that any touched entities must have a value - e.g. catering for a data migration. We leave it with you to update this to match your requirements rather than forcing this.
|
|