tag:blogger.com,1999:blog-8884584404576003487.post1543771663179373991..comments2024-02-29T09:43:12.251-05:00Comments on ORACLENERD: Design: The Entity = The Partyoraclenerdhttp://www.blogger.com/profile/12412013306950057961noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8884584404576003487.post-73164481427819394952008-09-03T10:09:00.000-04:002008-09-03T10:09:00.000-04:00Mr. Wurzbach how nice to see you finally. :)I don'...Mr. Wurzbach how nice to see you finally. :)<BR/><BR/>I don't recall anything specific but that doesn't mean it didn't happen. Much of what I now know was based on what I learned with you.<BR/><BR/>I wholly agree. Dev/testing should ultimately define the physical implementation.<BR/><BR/>I would disagree that I am hung up on the app dev vs database dev. It's been an observation the last few years that continues to pop up. I believe you provided an environment that was pretty well rounded...which is the ideal. It seems to get specialized in other places (either/or not and). Many of the app dev people don't know how the database works (sweeping generalization) and many data dev people don't understand the app side. <BR/><BR/>Plus, I don't know if there are that many smarter than you out there. ;)oraclenerdhttps://www.blogger.com/profile/12412013306950057961noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-11450596742975440602008-09-03T09:48:00.000-04:002008-09-03T09:48:00.000-04:00Um...We discussed an approach similar to this at L...Um...<BR/><BR/>We discussed an approach similar to this at <A HREF="http://www.lifesouth.org" REL="nofollow">LifeSouth</A> while you were employed here. The party table provided a common point for attaching addresses, phone numbers and other things common to a party/entity and supplemental tables held class specific data (e.g. a table for persons with blood types and cmv results, one for companies with terms, etc).<BR/><BR/>I don't know if it's an "app dev" person's favorite or not (as an aside, I think you're a little hung up on app dev vs. database dev--it's been argued both ways by smarter people than us). Parties and other archtypes are quite useful during schema modeling, but like everything else, during implementation it should be tested before the decision to keep the class/subclass model or flatten it is made.Tom Wurzbachhttps://www.blogger.com/profile/09389735548783500947noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-87706698658621591842008-09-02T07:37:00.000-04:002008-09-02T07:37:00.000-04:00Come on Dom...let me enjoy the moment! ;)I would ...Come on Dom...let me enjoy the moment! ;)<BR/><BR/>I would stick to the person and organization and perhaps subtypes of those. So not everything (I think).<BR/><BR/>So far I've seen that app dev people like it (more "object-oriented" I guess?), that in itself should scare me right?<BR/><BR/>chetoraclenerdhttps://www.blogger.com/profile/12412013306950057961noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-22349721042461884162008-09-02T03:48:00.000-04:002008-09-02T03:48:00.000-04:00aka the "Everything is a..." model, in the case "e...aka the "Everything is a..." model, in the case "everything is a party".<BR/><BR/>imho very overused and frequently underperforming.DomBrookshttps://www.blogger.com/profile/02598622186013843759noreply@blogger.com