[Django] #25379: Update GeoDjango tutorial to Postgres 9.1+ and CreateExtension
Django
-------------------------------+--------------------
Reporter: fcurella | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The GeoDjango tutorial () still instructs to create a db using the spatial
template.
Since PostgresSQL 9.1, the preferred way is to use the `postgis` extension
instead.
This brings up another issue: should `makemigrations` automatically add a
`CreateExtension` operation? Is that even doable?
For now I've simply documented it, but it would be very handy to have it
automatically.
--
Ticket URL: <https://code.djangoproject.com/ticket/25379>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: fcurella | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by fcurella):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> The GeoDjango tutorial () still instructs to create a db using the
> spatial template.
>
> Since PostgresSQL 9.1, the preferred way is to use the `postgis`
> extension instead.
>
> This brings up another issue: should `makemigrations` automatically add a
> `CreateExtension` operation? Is that even doable?
>
> For now I've simply documented it, but it would be very handy to have it
> automatically.
New description:
The GeoDjango tutorial
(https://docs.djangoproject.com/en/1.8/ref/contrib/gis/tutorial/) still
instructs to create a db using the spatial template.
Since PostgresSQL 9.1, the preferred way is to use the `postgis` extension
instead.
This brings up another issue: should `makemigrations` automatically add a
`CreateExtension` operation? Is that even doable?
For now I've simply documented it, but it would be very handy to have it
automatically.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25379#comment:1>
Django
Reporter: fcurella | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by fcurella):
initial PR https://github.com/django/django/pull/5265
--
Ticket URL: <https://code.djangoproject.com/ticket/25379#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: fcurella | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* has_patch: 0 => 1
* stage: Unreviewed => Ready for checkin
* type: Uncategorized => Cleanup/optimization
--
Ticket URL: <https://code.djangoproject.com/ticket/25379#comment:3>
Django
-------------------------------------+-------------------------------------
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"dfced0921c11f4ab9df8b036761b8965595e4416" dfced09]:
{{{
#!CommitTicketReference repository=""
revision="dfced0921c11f4ab9df8b036761b8965595e4416"
Fixed #25379 -- Removed obsolete information from GeoDjango tutorial.
Django 1.9 drops support for PostgreSQL 9.0 where creating
a database using a template was needed.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25379#comment:4>