I'd like to help fix a misapprehension, though. The subject was a methodology which helps people who write OO code and people who develop and maintain RDBMSs communicate frequently and fruitfully. As described, the communication begins when a project begins and continues on through its end. This in turn helps with perennial problems in communication between the respective components. You can find the slides at <a href="http://fetter.org/Database_As_Object_20060630.pdf" title="fetter.org">http://fetter.org/Database_As_Object_20060630.pdf</a fetter.org>
Database as Object
Posted by: dfetter on July 12, 2006 09:52 PMI'd like to help fix a misapprehension, though. The subject was a
methodology which helps people who write OO code and people who
develop and maintain RDBMSs communicate frequently and fruitfully. As
described, the communication begins when a project begins and
continues on through its end. This in turn helps with perennial
problems in communication between the respective components. You can
find the slides at <a href="http://fetter.org/Database_As_Object_20060630.pdf" title="fetter.org">http://fetter.org/Database_As_Object_20060630.pdf</a fetter.org>
#