home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!paladin.american.edu!gatech!usenet.ins.cwru.edu!agate!dog.ee.lbl.gov!news!humu!pegasus!tleylan
- From: tleylan@pegasus.com (Tom Leylan)
- Subject: Re: Info hiding v/s data abstraction
- Message-ID: <1992Dec27.075106.24834@pegasus.com>
- Organization: Pegasus, Honolulu
- References: <18923@mindlink.bc.ca>
- Date: Sun, 27 Dec 92 07:51:06 GMT
- Lines: 35
-
- John_Carson@mindlink.bc.ca (John Carson) writes:
- >> Yashesh Bhatia writes:
-
- >> Could someone let me know if there are dufferences between these two terms
- >> and if so what are the pro's and cons of using one for the other in the
- >> world of databeses and s/w eng.
- >
- >Data abstraction and hiding data.
- >
- >1) Data abstraction is removing the database #1 and placing into database #2
- >and based on a certain condition. Then manipulating it to your needs.
- >
- >2) Hiding data is like setting a filter so you only see what you want based
- >on the filter condition.
-
- John... Quick send a follow up message consisting of nothing more than a
- grin symbol before somebody thinks you meant this <g>
-
- Possibly you're describing "data extraction" and "database filtering" but
- that isn't (in my reading) what the question was about.
-
- Data abstraction and data hiding isn't even about "databases" particularly
- but rather "data" in the sense of "what's under the hood". Both are
- fundamental principles of OOPs programming and I switch between the two
- terms at will.
-
- You want to be able to write something similar to :
-
- nVar = MyBox:width
-
- and not be concerned whether "width" is a function which determines the
- width of the box or simply an attribute of a box which is returned.
-
- tom
-
-