Is it possible to ignore a system check error in Django 1.7+ -


i'm running following issue: have older (recently upgraded django 1.6) site uses one-to-one relations user profiles, fk references models pointing auth.user. i'm building site in 1.8 on separate subdomain uses same database old 1 , uses 2 apps old 1 has custom auth model class. know i'm doing , want different tables users of both sites. system check new site fails fields.e301 error:

core.recipientaccount.created_by: (fields.e301) field defines relation model 'auth.user', has been swapped out.         hint: update relation point @ 'settings.auth_user_model'. 

is possible work around this? or have use 1.6 new site or write lots of custom migrations refactor old one?

i've found solution problem time being. i'd refactor old project use custom user model of it's own. temporary fix using subclass of foreignkey reference django.contrib.auth.user skips check swapped model.

class foreignkeyskipsswappedcheck(models.foreignkey):      def check(self, **kwargs):         django.db.models.fields.related import relatedfield         errors = super(relatedfield, self).check(**kwargs)         errors.extend(self._check_related_name_is_valid())         errors.extend(self._check_relation_model_exists())         errors.extend(self._check_clashes())         return errors 

Comments

Popular posts from this blog

node.js - Using Node without global install -

How to access a php class file from PHPFox framework into javascript code written in simple HTML file? -

java - Null response to php query in android, even though php works properly -