Any thoughts on #13826 ? (geometry columns incompatible with sqlcustom)
3 views
Skip to first unread message
Paul Winkler
unread,
Nov 17, 2010, 10:50:17 PM11/17/10
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django developers
This bug has been outstanding for a while:
http://code.djangoproject.com/ticket/13826 Summary: with the postgis backend at least, and I believe for
spatialite and possibly others as well, you cannot leverage the
sqlcustom hook - because geometry columns aren't actually created
until the sqlindexes phase, which comes after the sqlcustom phase.
I kind of wonder if we're looking at this the wrong way. Ignoring the
more general desire for more hooks, maybe there's a way to move the
creation of geometry columns out of the sqlindex phase. I found it
very surprising that some columns are not created until that phase.