Re: Django 1.4.1, multiple geometry fields problem

Well bug was closed because it fixed the issue back then. I suspect that internals of query has been changed between 1.3 and 1.4 that causes now a new problem. Main issue is that when inserting or updating value cx_Oracle interpreted NULL value for OBJECT field when placeholder (%s) as a

Re: Django 1.4.1, multiple geometry fields problem

Well, the bug was closed. You can try inserting empty geometries, but then, you would need to recheck them if they are something before using. A property might suit you well in this case. if self.geometry.empty: > return None Hackish, but it's Oracle Spatial :o On Tue, Oct 2, 2012 at 9:49

Re: Django 1.4.1, multiple geometry fields problem

I guess all this is related to special munging required by Oracle: https://code.djangoproject.com/ticket/10888 2.10.2012 15:12, George Silva kirjoitti: Then it's probably Oracle, which is riddled with bugs on the spatial part. I'm using PostGIS. On Tue, Oct 2, 2012 at 8:38 AM, Jani Tiainen

Re: Django 1.4.1, multiple geometry fields problem

Then it's probably Oracle, which is riddled with bugs on the spatial part. I'm using PostGIS. On Tue, Oct 2, 2012 at 8:38 AM, Jani Tiainen wrote: > > 2.10.2012 14:34, Jani Tiainen kirjoitti: > > 2.10.2012 14:06, George Silva kirjoitti: >> >>> This is puzzling. I'm on 1.4.1

Re: Django 1.4.1, multiple geometry fields problem

2.10.2012 14:34, Jani Tiainen kirjoitti: 2.10.2012 14:06, George Silva kirjoitti: This is puzzling. I'm on 1.4.1 and I have models with two geometric columns, without a hitch. The only interesting thing I can see is that you are using SRID = settings.4326 on extent. Is that correct? Nope.

Re: Django 1.4.1, multiple geometry fields problem

2.10.2012 14:06, George Silva kirjoitti: This is puzzling. I'm on 1.4.1 and I have models with two geometric columns, without a hitch. The only interesting thing I can see is that you are using SRID = settings.4326 on extent. Is that correct? Nope. Normally it's something totally different

Re: Django 1.4.1, multiple geometry fields problem

This is puzzling. I'm on 1.4.1 and I have models with two geometric columns, without a hitch. The only interesting thing I can see is that you are using SRID = settings.4326 on extent. Is that correct? On Tue, Oct 2, 2012 at 7:52 AM, Jani Tiainen wrote: > Hi, > > I've

Django 1.4.1, multiple geometry fields problem

Hi, I've several models that contains two geometry fields (following is simplified example): class NetDiagram(models.Model): # Columns name = models.CharField(max_length=60, blank=True, null=True) location = models.GeometryField(_("Center"), db_column='location', srid=4326,