You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the django-examples, I noticed that the setting for SOCIAL_AUTH_STORAGE is commented out here. Is it because this override doesn't work as expected?
I've overriden the UserSocialAuth model similar to the example and added it a CustomDjangoStorage class and marked it with the SOCIAL_AUTH_STORAGE. But in the PostgresDB I notice tables created for the UserSocialAuth model as well. Is there any way to ensure they don't get created since we won't actually use them?
The text was updated successfully, but these errors were encountered:
Libraries used
From the django-examples, I noticed that the setting for
SOCIAL_AUTH_STORAGE
is commented out here. Is it because this override doesn't work as expected?I've overriden the
UserSocialAuth
model similar to the example and added it aCustomDjangoStorage
class and marked it with theSOCIAL_AUTH_STORAGE
. But in the PostgresDB I notice tables created for theUserSocialAuth
model as well. Is there any way to ensure they don't get created since we won't actually use them?The text was updated successfully, but these errors were encountered: