Do Objects Hide Implementation Details?
Some people say that Object-Relational is good because it allows us to hide the implementation details. More crud. The most common change is to add a new field to the database. This means we need to add a new field to the object-relational system, and we need to add code in our software to make use of the new field – so where is the data hiding? It’s irrelevant. The other common change is when we rename or redesign the table structures and we have applications that use the legacy data format. The best way to cope with this change is to use database views and instead-of triggers or rules. This ensures that we show a consistent view of the data to all applications, instead of changing the 10 Object-Relational interfaces for the 10 applications that feed on that legacy data. Is Combining Data and Methods Good? The other argument for Object-Relational is that objects combine data and methods to obtain better data-coupling… Yeah, like a strait-jacket. You can also argue that separating yo
