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 B01124758A5 for ; Tue, 16 Jul 2002 11:38:32 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g6GFcS925954; Tue, 16 Jul 2002 11:38:28 -0400 (EDT) From: Bruce Momjian Message-Id: <200207161538.g6GFcS925954@candle.pha.pa.us> Subject: Re: [SQL] line datatype In-Reply-To: <3D343BEA.1B51B9CD@fourpalms.org> To: Thomas Lockhart Date: Tue, 16 Jul 2002 11:38:28 -0400 (EDT) Cc: Tom Lane , 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/641 X-Sequence-Number: 25015 Thomas Lockhart wrote: > ... > > > We do need a solution for exact dump/reload of floating-point data, > > > but I don't see why the lack of it should be reason to disable access > > > to the LINE type. > > I don't understand why dumping the two point values isn't sufficient. > > Which two point values? LINE is handled as an equation, not as points, > unlike the LSEG type which has two points. Well, the \dT documentation used to show line as two points, so I assumed that was how it was specified. > One possibility is to have the external representation *be* the same as > LSEG, then convert internally. Then we need to decide how to scale those > points; maybe always using a unit vector is the right thing to do... No one likes entering an equation. Two points seems the simplest. -- 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