hey guys, take a look at this, it saved my live on today.
https://github.com/django/django/pull/249
El lunes, 6 de agosto de 2012 10:28:50 UTC-5, Oleg Korsak escribió:
>
> Have you tried to create new project, then new app, then new model with
> PointField(geography=False) and then run manage.p
Have you tried to create new project, then new app, then new model with
PointField(geography=False) and then run manage.py syncdb? Here must be a
problem :)
суббота, 4 августа 2012 г., 8:59:34 UTC+3 пользователь Will
Tuladhar-Douglas написал:
>
> Folks,
>
> I just checked and I'm running Postg
Folks,
I just checked and I'm running Postgres 9.1 and Postgis 2.0SVN with GeoDjango
(on Mac OSX 10.7.4) . I'm not doing anything very exciting with GeoDjango so
far, so perhaps there are problems I haven't encountered, but it does run, and
it is possible to encode locations using the GeoDjango
On Aug 3, 2012, at 3:55 PM, Thomas Lockhart wrote:
> Really? What is the use case requiring a version 2.0.0?
PostGIS 2.0 has a lot of stuff in it, including things like KNN indexes; those
alone are worth upgrading for.
> And typically folks don't jump on a x.0.0 of anything, expecting to see it
On 8/3/12 3:39 PM, Oleg Korsak wrote:
looks like GeoDjango is dead, it is not solved for almost half of the year
Really? What is the use case requiring a version 2.0.0? Seems that the
previous 1.x version works as advertised.
And typically folks don't jump on a x.0.0 of anything, expecting to
looks like GeoDjango is dead, it is not solved for almost half of the year
четверг, 19 июля 2012 г., 21:23:03 UTC+3 пользователь Dominique Guardiola
Falco написал:
>
>
> Is there a tutorial describing how to do this somewhere please ?
> Because right now, geodjango is unusable with PostGreSQL 9 +
Is there a tutorial describing how to do this somewhere please ?
Because right now, geodjango is unusable with PostGreSQL 9 + PostGIS 2
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.goo
On Apr 7, 2012, at 12:01 PM, Oleg Korsak wrote:
> sorry? which one SQL? :) I'm trying to run tests with Jenkins CI, but
> it fails on creating DB.
Ah, OK. The automated tests will probably fail, yes. For your application,
you can work around this problem by manually created the indexes rather
sorry? which one SQL? :) I'm trying to run tests with Jenkins CI, but
it fails on creating DB.
7 апреля 2012 г. 21:56 пользователь Christophe Pettus
написал:
>
> On Apr 7, 2012, at 11:41 AM, Oleg Korsak wrote:
>
>> So looks PostGIS 2.0.0 is unusable with Django right now?
>
> There's no reason y
On Apr 7, 2012, at 11:41 AM, Oleg Korsak wrote:
> So looks PostGIS 2.0.0 is unusable with Django right now?
There's no reason you can't apply the SQL manually for the moment.
--
-- Christophe Pettus
x...@thebuild.com
--
You received this message because you are subscribed to the Google Grou
Hello. After upgrading PostGIS to 2.0.0 version and migrating DB (took
some time) I still have one problem:
django.db.utils.DatabaseError: operator class "gist_geometry_ops" does
not exist for access method "gist"
I've found a discussion here: https://code.djangoproject.com/ticket/16455
So looks
11 matches
Mail list logo
