Thank you for your help. Even though I understand the obvious reason to use the in-built User model I prefer to make one myself. Not because the integrated one is bad. It is just that it adds huge amounts of boilerplate and hidden django magic. And since users are basically just a name and an identifier and present everywhere on the internet I chose to use them to learn how to interface DBs with Django.
Also I used the tutorial just that I abstracted the concept since I think the tutorial is more than bad. In addition this method teaches on what essentially I am doing else then to blindly copying code. Thanks Peter Am Sonntag, 15. Januar 2017 22:11:30 UTC+1 schrieb Mike Dewhirst: > > On 16/01/2017 5:01 AM, 'Peter Müller' via Django users wrote: > > Hello everybody. > > > > > > I just began learning how to use django. So I wanted to include data > > from the database in a testwebsite. > > Therefore I made a new app and created a model called "user" and > > You don't need to create your own user model. There's one in the box ... > > from django.contrib.auth.models import User > > Try using that and see if your error goes away. Also, you should work > through the tutorial to get a handle on how it is used ... > > https://docs.djangoproject.com/en/1.10/intro/tutorial01/ > > As you are a Django beginner I assume you will try one or two small > projects before tackling a major one so just going with the standard > User model should be no impediment in the early stages. Then maybe look > through the docs to see how to customise/replace that User model. > > Cheers > > Mike > > > a view that should fill a template with data from that model. > > To do this (according to Django 1.10 Docs/Tutorial) I need to import > > the model class into the view file and for example use > models.user.all(). > > However on import of the view Django complains about > > | > > django.core.exceptions.AppRegistryNotReady:Appsaren't loaded yet > > | > > > > What is the solution to that problem? > > > > Greetings > > Peter > > -- > > You received this message because you are subscribed to the Google > > Groups "Django users" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to django-users...@googlegroups.com <javascript:> > > <mailto:django-users+unsubscr...@googlegroups.com <javascript:>>. > > To post to this group, send email to django...@googlegroups.com > <javascript:> > > <mailto:django...@googlegroups.com <javascript:>>. > > Visit this group at https://groups.google.com/group/django-users. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/django-users/31442c04-4da4-496b-8611-9d7b70e36138%40googlegroups.com > > > < > https://groups.google.com/d/msgid/django-users/31442c04-4da4-496b-8611-9d7b70e36138%40googlegroups.com?utm_medium=email&utm_source=footer>. > > > > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/442d8301-3521-40fc-9adc-9150ca0cfeab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
