Subject: Re: Row vs. tuple
From: Hannu Krosing <hannu@tm.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sean Chittenden <sean@chittenden.org>,
	Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org
In-Reply-To: <15712.1047763882@sss.pgh.pa.us>
References: <Pine.LNX.4.44.0303141647200.2382-100000@peter.localdomain>
	<25320.1047690393@sss.pgh.pa.us>
	<20030315210321.GO79234@perrin.int.nxad.com>
	<15712.1047763882@sss.pgh.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1048626064.1675.6.camel@fuji.krosing.net>
Mime-Version: 1.0
Date: 25 Mar 2003 23:01:05 +0200

Tom Lane kirjutas L, 15.03.2003 kell 23:31:
> Sean Chittenden <sean@chittenden.org> writes:
> > How about:  s/(row|tuple)/record/
> 
> We do need two different terms: eliminating the distinction between a
> row and a version of a row is not going to improve matters.

For me "row version" is a nice, self-explaining term. There is very
little chance that you will misake it for anything else, from whatever
culture (math,db,bean-counting,hardware hacking,...) you come from.

Tuple and record are both already loaded with several different and
contradicting meanings.

> I have nothing against the word "record", but it doesn't seem to help
> clarify this distinction ...

True.

-----------
Hannu