Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 8540C475E76 for ; Tue, 16 Jul 2002 12:31:53 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g6GGVnT02128; Tue, 16 Jul 2002 12:31:49 -0400 (EDT) From: Bruce Momjian Message-Id: <200207161631.g6GGVnT02128@candle.pha.pa.us> Subject: Re: [SQL] line datatype In-Reply-To: <13299.1026837027@sss.pgh.pa.us> To: Tom Lane Date: Tue, 16 Jul 2002 12:31:49 -0400 (EDT) Cc: Thomas Lockhart , Tim Hart , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200207/654 X-Sequence-Number: 25028 Tom Lane wrote: > Thomas Lockhart writes: > >> No one likes entering an equation. Two points seems the simplest. > > > That it does. > > On the other hand, if you want to enter two points why don't you just > use lseg to begin with? There's not much justification for having a > separate line type unless it behaves differently ... I assume the line type keeps going after the two end points, while lseg doesn't. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026