Comments on: Explain it: Database http://industryinteractive.net/customer-service/explain-it-database/ web consulting and online services Fri, 21 Nov 2008 17:19:22 +0000 http://wordpress.org/?v=2.6 By: J Lopez http://industryinteractive.net/customer-service/explain-it-database/#comment-70 J Lopez Fri, 04 Apr 2008 15:19:15 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-70 The way I have explained it is a file cabinet. since a database was made to replace it. File cabinet = database File drawer = Table File = Record Everything after that gets technical and harder to explain. fields, relationships, search, index, etc. The way I have explained it is a file cabinet. since a database was made to replace it.
File cabinet = database
File drawer = Table
File = Record

Everything after that gets technical and harder to explain.
fields, relationships, search, index, etc.

]]> By: Scott Skjei http://industryinteractive.net/customer-service/explain-it-database/#comment-56 Scott Skjei Thu, 20 Mar 2008 00:20:50 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-56 I think of a database as a kind of "super" index. Most people understand what an index in a book is. Imagine looking up WW2 in some first year world history text. You'd find pages where WW2 is discussed. Now imagine looking up England in the same book. A database would let you find all the pages that discuss WW2 and England, WW2 but not England, WW2 or England, etc. Do I completely misunderstand databases? I think of a database as a kind of “super” index. Most people understand what an index in a book is. Imagine looking up WW2 in some first year world history text. You’d find pages where WW2 is discussed. Now imagine looking up England in the same book. A database would let you find all the pages that discuss WW2 and England, WW2 but not England, WW2 or England, etc.

Do I completely misunderstand databases?

]]> By: Kim Siever http://industryinteractive.net/customer-service/explain-it-database/#comment-44 Kim Siever Wed, 19 Mar 2008 03:40:14 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-44 It's like a big Excel spreadsheet. An analogy could be a big file cabinet. Each cabinet is a database. Each drawer is a table. Each folder is a row. It’s like a big Excel spreadsheet.

An analogy could be a big file cabinet. Each cabinet is a database. Each drawer is a table. Each folder is a row.

]]> By: Kim Siever http://industryinteractive.net/customer-service/explain-it-database/#comment-38 Kim Siever Tue, 18 Mar 2008 20:01:39 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-38 The website is like the robotic secretary who extracts file folders at superhuman speed. The website is like the robotic secretary who extracts file folders at superhuman speed.

]]> By: J Lane http://industryinteractive.net/customer-service/explain-it-database/#comment-37 J Lane Tue, 18 Mar 2008 18:41:55 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-37 Cool, yeah. I pulled out the "filing cabinet" one once, but it breaks down a bit if you're trying to explain what purposed a database serves in a web site. Cool, yeah. I pulled out the “filing cabinet” one once, but it breaks down a bit if you’re trying to explain what purposed a database serves in a web site.

]]> By: Michael Warf http://industryinteractive.net/customer-service/explain-it-database/#comment-36 Michael Warf Tue, 18 Mar 2008 16:05:37 +0000 http://industryinteractive.net/customer-service/explain-it-database/#comment-36 I don't have a reference for databases in particular Jon, but when I taught at GMCC I had to explain foundational coding concepts to people who's primary background was visual design. I would describe variables as temporary "holes in your garden" where you could temporarily store items for later retrieval. Datatypes became the signposts on the row "carrots, peas, corn" - people seemed to get it (although I'm a whiteboard maniac - so my explanation would be 50% visual) I would describe indexed arrays as "filing cabinets", that allow you to temporarily store items individually, but together in a larger sense. And, of course - the old "lego brick" metaphor for OOP concepts. M. I don’t have a reference for databases in particular Jon, but when I taught at GMCC I had to explain foundational coding concepts to people who’s primary background was visual design.

I would describe variables as temporary “holes in your garden” where you could temporarily store items for later retrieval. Datatypes became the signposts on the row “carrots, peas, corn” - people seemed to get it (although I’m a whiteboard maniac - so my explanation would be 50% visual)

I would describe indexed arrays as “filing cabinets”, that allow you to temporarily store items individually, but together in a larger sense.

And, of course - the old “lego brick” metaphor for OOP concepts.

M.

]]>