Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
How to avoid: 9.50184e+06
- From: Stefan Schwarzer <stefan(dot)schwarzer(at)grid(dot)unep(dot)ch>
- To: pgsql-general(at)postgresql(dot)org
- Subject: How to avoid: 9.50184e+06
- Date: Fri, 28 Sep 2007 14:08:18 +0200
| Hi there, how can I avoid results like this: 9.50184e+06 Instead it should return the "real" value, as 950184. Thanks for any hints! Stef ____________________________________________________________________
Lean Back and Relax - Enjoy some Nature Photography: Appetite for Global Data? UNEP GEO Data Portal: ____________________________________________________________________ |
- Follow-Ups:
- Re: How to avoid: 9.50184e+06
- From: Ted Byers
- Re: How to avoid: 9.50184e+06
- From: Scott Marlowe
- Re: How to avoid: 9.50184e+06
- From: Martijn van Oosterhout
- Re: How to avoid: 9.50184e+06
- From: Merlin Moncure
- Re: How to avoid: 9.50184e+06
- Prev by Date: Re: Why the ERROR: duplicate key violates unique constraint "master_pkey" is raised? - Is this a Bug?
- Next by Date: Re: How to avoid: 9.50184e+06
- Previous by thread: usage of indexes for inner joins
- Next by thread: Re: How to avoid: 9.50184e+06
- Indexes: