Approach to use for user email address change in application?
As the title says, if the user wants change their email address in the application, in terms of programming, what approach (process) to use? Where do you store the new email address until the user will confirms it?
Approach to use for user email address change in application?
As the title says, if the user wants change their email address in the application, in terms of programming, what approach (process) to use? Where do you store the new email address until the user will confirms it?
Complex Mutual Exclusion Validation Logic
I need to validate some form inputs in complex way. E.g.
Best Practice for Argument Checking
Say I have a web service with a method MyWebServiceMethod(string passedValue).
If the model is validating the data, shouldn’t it throw exceptions on bad input?
Reading this SO question it seems that throwing exceptions for validating user input is frowned upon.
Where to validate domain model rules that depend on database content?
I’m working on a system that allows Administrators to define Forms that contain Fields. The defined Forms are then used to enter data to the system. Sometimes the Forms are filled by a human via a GUI, sometimes the Form is filled based on values reported by another system.
Where to validate domain model rules that depend on database content?
I’m working on a system that allows Administrators to define Forms that contain Fields. The defined Forms are then used to enter data to the system. Sometimes the Forms are filled by a human via a GUI, sometimes the Form is filled based on values reported by another system.
Where to validate domain model rules that depend on database content?
I’m working on a system that allows Administrators to define Forms that contain Fields. The defined Forms are then used to enter data to the system. Sometimes the Forms are filled by a human via a GUI, sometimes the Form is filled based on values reported by another system.
Validation and data persistence in a domain model
My (first and current) workplace (a .NET shop) suffers from an over-abundance of anemic domain models, to the extent that I don’t really know how validation and data persistence should be handled in a proper domain model.
Validation and data persistence in a domain model
My (first and current) workplace (a .NET shop) suffers from an over-abundance of anemic domain models, to the extent that I don’t really know how validation and data persistence should be handled in a proper domain model.