public inbox for [email protected]  

help / color / mirror / Atom feed

From: Sean Chittenden <[email protected]>
To: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Row vs. tuple
Date: Sat, 15 Mar 2003 13:03:21 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

> > In some places the documentation uses the term "tuple" to mean
> > "row version" (in the MVCC sense).  This choice of terms is
> > puzzling me; where does it come from?  In the literature available
> > to me, the term "tuple" is used as the mathematical equivalent of
> > "row", meaning that table/row/column parallels
> > relation/tuple/attribute.
> 
> Well, "row version" isn't a particularly standard term either.  I'd
> prefer a one-word term.  I think that the use of "tuple" for this can be
> traced back to the Berkeley code.

How about:  s/(row|tuple)/record/

A "record" is a much less theoretical/mathematical term that I've had
good success in using when describing basic table theory to lay
people.  Seems easier to grasp on the uptake than a row (rows are
confused with columns if you're not familiar with databases, math, or
matrices.  "Do rows go vertically or horizontally?") or tuple
(heavily mathematical term or term used in DB theory, but no where
else).  A record, on the other hand, is something that everyone has a
conceptual picture of.  -sc

-- 
Sean Chittenden

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Row vs. tuple
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox