Received: from www.wgcr.org (www.wgcr.org [206.74.232.194]) by postgresql.org (Postfix) with ESMTP id CF00A4758A7 for ; Tue, 16 Jul 2002 16:50:06 -0400 (EDT) Received: from localhost.localdomain ([10.1.2.112]) by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id QAA15937; Tue, 16 Jul 2002 16:49:58 -0400 Content-Type: text/plain; charset="iso-8859-1" From: Lamar Owen To: Thomas Lockhart , Tom Lane Subject: Re: [SQL] line datatype Date: Tue, 16 Jul 2002 16:46:57 -0400 User-Agent: KMail/1.4.1 Cc: Bruce Momjian , Tim Hart , PostgreSQL-development References: <200207161538.g6GFcS925954@candle.pha.pa.us> <13299.1026837027@sss.pgh.pa.us> <3D348526.CC9594FD@fourpalms.org> In-Reply-To: <3D348526.CC9594FD@fourpalms.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200207161646.57963.lamar.owen@wgcr.org> X-Archive-Number: 200207/663 X-Sequence-Number: 25037 On Tuesday 16 July 2002 04:42 pm, Thomas Lockhart wrote: > > 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 ... > They are different. One is infinite in length, the other is finite. > Distances, etc are calculated differently between the two types. For some of my work a type of 'ray' would be nice... :-) But LSEG's usually work OK as long as you specify an endpoint that is far enough away. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11