Any thoughts on #13826 ? (geometry columns incompatible with sqlcustom)

Skip to first unread message

Paul Winkler

Nov 17, 2010, 10:50:17 PM11/17/10
to Django developers
This bug has been outstanding for a while:
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.

It could be approached as a specific case of a more general problem
ticketed here:
... about which I found some inconclusive discussion here:

Any thoughts on the right solution here?

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.
Reply all
Reply to author
0 new messages