I understand this is a matter of design and can be subjective, but some advice on what should be in a domain object (especially for the previous example with a profile) and if they need to followmarry up to a table or not would be helpful.
I understand this is a matter of design and can be subjective, but some advice on what should be in a domain object (especially for the previous example with a profile) and if they need to follow a table or not would be helpful.
I understand this is a matter of design and can be subjective, but some advice on what should be in a domain object (especially for the previous example with a profile) and if they need to marry up to a table or not would be helpful.
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in.
Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object or? Or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile? Is it a good idea to have more than one domain object?
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in. Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile? Is it a good idea to have more than one domain object?
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in.
Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object? Or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile?
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in. Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile? Is it a good idea to have more than one domain object for a forum web application?
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in. Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile? Is it a good idea to have more than one domain object for a forum web application?
This is where I’m confused as to what exactly a domain object should be. I understand they should encompass business logic, but identifying what business logic I would need for a forum application is proving difficult. For example I would like each user to have their own profile page that is publicly visible, that they can only edit and update when the user in question is logged in. Would I need to create a ‘profile’ domain object together with a new profile table that links to my original user table and user domain object or could I simply extend my existing user table and user domain object to have properties and methods that can allow a user to display and update their profile? Is it a good idea to have more than one domain object?
Loading
lang-php