Week 46, year 2013

• Value Objects and User Interfaces - I got this mail from a listener of the podcast episode on Value Objects I recorded with Konstantin: I've been listening to your Elephant in the room podcast Episode #002, i was wondering if you have a coding example of where you use the Country as a value object and not as an entity. I've come across this problem too, and was hoping you may have an example that i can look at to give me a better understanding in terms of how to code this? My first question would really be how would you logically store a list of all countries outside of a database if you were using value objects for use in a Form lookup field? There’s nothing intrinsically wrong with modelling countries as entities and storing them in the database. But in most cases, that overcomplicating things. Countries don’t change often. When a country’s name changes, it is in fact, for all practical purposes, a new country. If a country one day does not exist anymore, you can’t simply change all addresses, because possibly the country was split into two countries. [Mathias Verraes]

Permalink | From 11 November 2013 to 17 November 2013 | Last updated on: Mon, 7 Jun 2021 09:18:52 GMT