#16455: Postgis 2.0 Compatibility
-------------------------------------+-------------------------------------
Reporter: ckarrie | Owner: jbronn
Type: New feature | Status: closed
Component: GIS | Version: master
Severity: Normal | Resolution: fixed
Keywords: postgis 2.0 | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by tomlesters@…):
some question regarding the above fcurella comment:
1.
The original patch had a suboptimal implementation. It has one additional
query on creation. This happens on database/table creation time or some
other time?
In my opinion, If it's only on database/table creation time the
performance impact is not a big concern.
2.
If we want to get rid of the additional query, Shouldn't we instruct the
user to create database the new way without templates since that's the way
postgis moving towards?
regarding petrounias comments:
any custom SQL was being generated after syncdb, any technique details on
why that failed?
wish to see this patch in the next django 1.4.x release!
--
Ticket URL: <https://code.djangoproject.com/ticket/16455#comment:66>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
