Posted by: Mark Fontecchio
The bloggers over at iDevelop recommend updating your DB2 lingo so all the Oracle and SQL Server folks don’t think you’re from the 1970s.
Why? Well, not just because using the old lingo makes you seem old, but also because it makes DB2 seem old, outdated, and not as powerful as iDevelop believes it to be.
Oracle and other database users are often convinced that what we have is little more than a flat file system on top of which has been cobbled some half-baked database mechanism. If you think about it, it’s hardly surprising. We constantly talk old-technology terms like files and records, so we shouldn’t be surprised if others think that that they are the foundation of the system.
Of course nothing could be further from the truth. What we have is a fully relational database system which, when called upon, can cleverly disguise itself as a flat file system! Those of us who use the platform can understand what a terrific advantage this is–but it’s understandable that others would view it with suspicion.
So here is the translation dictionary, with the DB2 word followed by the “updated” DB2 word:
- A library should now be called a schema or collection
- A file should be called a table
- A record should be called a row
- A field should be called a column
- A logical file should be called a view when talking about how the program views the data
- A logical file should be called an index when talking about performance