On 08/25/2010 02:19 PM, Sam Walters wrote:
I would need the answer evaluated as quickly as possible, radius
calculation would be slower (how much slower depends on the algorithm
used and other variables).
One of my colleagues tells me the database-internal (so:
postgresql+postgis and so) calcu
Thanks for the replies.
No its not 32 bit/64 bit issue. (both 64 bit and its not a floating
point issue anyway)
Correct: I dont need to *have* the problem except some of the
requirements in the project require passing of 8 decimal place
lat/longs in the url.
I was hoping not to have to take steps
Is one server 32 bit, while the other is 64 bit? It may be that on the old
server, your representations of the number were precise enough to be identical,
but on the new server, there is enough precision in the database to represent
different numbers.
"Reinout van Rees" wrote:
>On 08/25/20
On 08/25/2010 02:57 AM, Sam Walters wrote:
Hi fellow Django developers
I have Lat/Lng points stored in my db:
class Airfield(models.Model):
point = models.PointField(srid=4326)
I noticed when i query on my development server with postgresql i DONT
have to have the EXACT number of decimal
Hi fellow Django developers
I have Lat/Lng points stored in my db:
class Airfield(models.Model):
point = models.PointField(srid=4326)
I noticed when i query on my development server with postgresql i DONT
have to have the EXACT number of decimal places to find that point.
(what i want)
Howev
5 matches
Mail list logo
