This week, Mike Gorman will be talking about Database Objects!
Starting in the late 1970s, Objects starting to be all the rage. My olde boss (now deceased) at Yourdon, Inc, Matt Flavin, created something called Database Object Classes. Now, because Matt was my boss, I ‘accepted’ it as great! Now, however, I know it is. At the time, we, Yourdon-database teachers, all taught it, students marveled at it, but frankly nobody really knew what it meant or what its value really was.
About in the middle 1990s, along came Clarion’s Classes. What were they? Not what Matt Flavin had put forward in the late 1970s. Not SQL Objects. And not the Business Objects community invented. While Clarion’s Classes are unique, they have all the trappings of object-stuff: Inheritance, Polymorphism, data definition, and methods (a.k.a., processes). You use them in the development of Clarion applications that included use of Clarion’s method-enhanced data management language.
OK, it now seems that for the past 45 years we have had multiple uses of the string “Object” with the only common characteristic that “nobody” agrees with anybody else on what it means, what it s good for and finally, what it does. That said, the “requirements” for Mike Gorman’s Database Object Classes presentation are:
● It has to be understandable
● It has to be valuable
● It has to be implementable
● It has to be able to accomplishable with the tools we already have
In short, it has to be what Matt Flavin actually intended back the late 1970s