| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Bryan White" <bryan(at)arcamax(dot)com> |
| Cc: | "Jeff Eckermann" <jeff_eckermann(at)yahoo(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: COPY Error Message is Confusing |
| Date: | 2002-04-10 22:56:01 |
| Message-ID: | 23808.1018479361@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Bryan White" <bryan(at)arcamax(dot)com> writes:
>> It's not strictly a "tuple" until it's been loaded.
> I guess that depends on your definition of 'tuple'. Are the rows returned
> by a select statment tuples if the select is a join of multiple tables. I
> tend to think of a tuple as an ordered set of values but maybe I have it
> wrong. In any event anyone of 'tuple', 'record', or 'row' would be less
> confusing than 'line'.
I agree that 'line' seems confusing in the presence of escaped newlines.
I prefer 'row' or possibly 'record' to 'tuple', however. 'tuple'
strikes me as unnecessarily jargon-ish in this context.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-10 23:02:13 | Re: Critical performance problems on large databases |
| Previous Message | Tom Lane | 2002-04-10 22:54:19 | Re: Multiply and Divide operators for geometry types |