It seems like a bug to me. If I had to guess, I'd say it's a multi-database setup that no one thought to test when the system check framework was developed.
On Friday, April 24, 2015 at 3:49:03 PM UTC-4, Ion Scerbatiuc wrote: > > Hello, > > Wasn't sure if this is a bug or not, and I couldn't find any related > tickets on https://code.djangoproject.com > > We have the following database set-up: > > - the default database is MySQL > - two additional databases are PostGIS > > The system check framework (either `manage.py check` or `manage.py > runserver`) is using the default database (mysql) to validate > `django.contrib.gis.db.models.Model`-based models, and the commands are > blowing up with the following error: > AttributeError: 'DatabaseOperations' object has no attribute > 'geo_db_type'. > > You can find the detailed stack trace here: > https://gist.github.com/delinhabit/587d6f26afb4bbc559cb > > We set-up database routers for the PostGIS models to use the proper > connection, but the check framework seems to ignore them. > Are we doing something wrong? > Is this a known pitfall of the system check framework around multiple > databases that we are unaware of? > Or is this a bug? > > Thanks, > Ion > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/701a49c0-84e5-46cf-a002-d7eaa990f5c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
