#23966: Doing pre-migrate database requirements
-------------------------------------+-------------------------------------
     Reporter:  kenial               |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |                  Version:  1.7
    Component:  Database layer       |               Resolution:
  (models, ORM)                      |             Triage Stage:
     Severity:  Normal               |  Unreviewed
     Keywords:  migrate              |      Needs documentation:  0
  BaseDatabaseWrapper spatialite     |  Patch needs improvement:  0
    Has patch:  0                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by kenial):

 Perhaps ... if InitSpatialMetaData query is executed in
 init_connection_state() method, then it will check it **every time when
 opening a connection**.  As you know, there is no connection pooling on
 sqlite3 (and SpatiaLite) by default. It means that every query will
 execute `PRAGMA table_info(geometry_columns);`, I don't think it's a right
 way.

 How about merging document stuff from pull request #3697 into mine? I
 forgot to update document about this.

--
Ticket URL: <https://code.djangoproject.com/ticket/23966#comment:5>
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/064.038d1b2b5521c686b2e6797a14377d2d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to