Comments on: Change the Code : DBA/Designer always has to look out for the third dimension http://www.orcasoracle.org/2006/08/09/change-the-code-dbadesigner-always-has-to-look-out-for-the-third-dimension/ Some experiences out of my daily oracle practice Tue, 06 Jan 2009 20:16:14 +0000 http://wordpress.org/?v=2.0.2 by: carl.reitschuster http://www.orcasoracle.org/2006/08/09/change-the-code-dbadesigner-always-has-to-look-out-for-the-third-dimension/#comment-948 Thu, 10 Aug 2006 08:47:09 +0000 http://www.orcasoracle.org/2006/08/09/change-the-code-dbadesigner-always-has-to-look-out-for-the-third-dimension/#comment-948 Thanks Alex for your update! This shows to me in every area (not only database) you have to work with complexity due to flexiblity the customer want's to have. The thing with the data is that it's frequntly ignored (who cares for data?) and then causes a lot of pain. Karl Thanks Alex for your update!
This shows to me in every area (not only database) you have to work with complexity due to flexiblity the customer want’s to have.

The thing with the data is that it’s frequntly ignored (who cares for data?) and then causes a lot of pain.
Karl

]]> by: Alexander http://www.orcasoracle.org/2006/08/09/change-the-code-dbadesigner-always-has-to-look-out-for-the-third-dimension/#comment-947 Thu, 10 Aug 2006 08:41:08 +0000 http://www.orcasoracle.org/2006/08/09/change-the-code-dbadesigner-always-has-to-look-out-for-the-third-dimension/#comment-947 That's a typical DBA point of view (just teasing ;-) ). Just one example: Suppose I have a WebService that publishes customer data. Now the customer data structure changes (say, "I need the customers favorite color for marketing purposes!"). You (in principle) don't know who consumes the web service. You cannot break existing consumers. What do you do? Answer: Support both versions at the same time! I.e. the web service should detect the version the client is using in his request and also shape the response accordingly. So we have two different versions active at the same time (whereas the database is always in exactly one defined version). Ergo: the dimensions of complexity may be different but versioning is a pain in the a**, no matter at which end of the application you work. Just my 0,02€ That’s a typical DBA point of view (just teasing ;-) ).

Just one example: Suppose I have a WebService that publishes customer data. Now the customer data structure changes (say, “I need the customers favorite color for marketing purposes!”). You (in principle) don’t know who consumes the web service. You cannot break existing consumers. What do you do?
Answer: Support both versions at the same time! I.e. the web service should detect the version the client is using in his request and also shape the response accordingly. So we have two different versions active at the same time (whereas the database is always in exactly one defined version).

Ergo: the dimensions of complexity may be different but versioning is a pain in the a**, no matter at which end of the application you work.

Just my 0,02€

]]>