| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Tim Hart <tjhart(at)mac(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [SQL] line datatype |
| Date: | 2002-07-16 15:21:05 |
| Message-ID: | 200207161521.g6GFL5417443@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Tom Lane wrote:
> Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
> > The issue is in choosing an external format for LINE which does not lose
> > precision during dump/reload.
>
> Why is this any worse for LINE than for any of the other geometric
> types (or for plain floats, for that matter)?
>
> 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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-07-16 15:29:46 | Re: [SQL] line datatype |
| Previous Message | Jan Wieck | 2002-07-16 14:22:20 | Re: pg_views.definition |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-07-16 15:29:46 | Re: [SQL] line datatype |
| Previous Message | Tom Lane | 2002-07-16 13:44:14 | Re: [SQL] line datatype |