#20968: Add a migrate hook for automatically running database setup SQL
-------------------------------------+-------------------------------------
     Reporter:  burton449geo@…       |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |                  Version:  master
    Component:  Database layer       |               Resolution:  fixed
  (models, ORM)                      |             Triage Stage:  Ready for
     Severity:  Normal               |  checkin
     Keywords:  geodjango,           |      Needs documentation:  0
  spatialite, indexes                |  Patch needs improvement:  0
    Has patch:  1                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8f97413faed5431713c034897cda486507bf0cc3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f97413faed5431713c034897cda486507bf0cc3"
 Fixed #20968 -- Checked Spatialite metadata before migrations

 Thanks Kenial S. Lee for the initial patch and Tim Graham for
 the review.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/20968#comment:17>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.a3580a00e9f5785e0375e6c723ff1a80%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to