Syncdb doesn't honor managed=False setting with Geodjango

[Jani Tiainen]

Geodjango "geomanager" based models do not honor "managed = False" setting but tries to forcefully create spatial index and insert spatial metadata in Oracle.

[mal]

It seems to happen when model (with spatial field) is based on the view.

When model points to the normal table (via db_table = 'my table') syncdb works alright (obeying "managed = False"), when it points to the view then syncdb keeps trying to install it, including attempts to create spatial medatada and spatial indexes.

Installing custom SQL for myapp.mymodel model
Failed to install custom SQL for myapp.mymodel model: ORA-13223: duplicate entry for <mytable>.location in SDO_GEOM_METADATA
ORA-06512: at "MDSYS.MD", line 1723
ORA-06512: at "MDSYS.MDERR", line 17
ORA-06512: at "MDSYS.SDO_GEOM_TRIG_INS1", line 48
ORA-04088: error during execution of trigger 'MDSYS.SDO_GEOM_TRIG_INS1'

[jbronn]

This is currently fixed in trunk, because GeometryField no longer uses the post_create_sql hook. However, for API consistency I will commit a fix for the post_create_sql hook to both trunk and 1.1.X (which is still affected). Moreover, this is not an Oracle-specific bug, as it affects all backends.

[jbronn]

(In [12313]) Fixed #11969 -- Field.post_create_sql hook should not be called for unmanaged models. Thanks, jtiai for report.

[jbronn]

(In [12314]) [1.1.X] Fixed #11969 -- Field.post_create_sql hook should not be called for unmanaged models. Thanks, jtiai for report.

Backport of r12313 from trunk.

[Jacob]

Milestone 1.2 deleted