Your question is very unclear. You should probably go through the django-tutorial. But sure you can insert data into the db from views. Assume you have a model called Foo: models.py class Foo(models.Model): name = models.CharField(max_length=100) view.py from .models import Foo def some_name(request): foo_instance = Foo.objects.create(name=”test”) return render(request, ‘some_name.html.html’)
You could use Q objects for #1: # Blogs who have either hockey or django tags. from django.db.models import Q Blog.objects.filter( Q(tags__name__iexact=”hockey”) | Q(tags__name__iexact=”django”) ) Unions and intersections, I believe, are a bit outside the scope of the Django ORM, but its possible to to these. The following examples are from a Django application called … Read more
SOLVED! the way to do this – from django.template.loader import render_to_string rendered = render_to_string(‘my_template.html’, { ‘foo’: ‘bar’ }) thanks to ned for pointing to the Django docs
For any further visitors of this thread, yes, you can make a FormView that acts like both a CreateView and an UpdateView. This, despite some opinions of other users, can make a lot of sense if you want to have a single form/URL/page for a web form to save some user data which can be … Read more
I think the best way to accomplish this is to call none() on objects for your respective model, and return the result. Assuming your model is named Entry: queryset = Entry.objects.none()
You need use as_view() at the end of class based views when declaring in the urls: path(”, views.HomeView.as_view(), name=”homepage”), Also, when using login_required decorator, you need to use it on dispatch method of CBV: from django.contrib.auth.decorators import login_required from django.utils.decorators import method_decorator class HomeView(ListView): @method_decorator(login_required) def dispatch(self, *args, **kwargs): return super(HomeView, self).dispatch(*args, **kwargs)
Thanks to the #django channel on Freenode IRC, I found the following method is the correct one to pass parameters all the way through to the view: response = DeviceView.as_view()(request, pk=1) I hope this helps somebody else attempting to use RequestFactory to test DetailView or DeleteView etc
{{request.GET.param1}} in the template. (Using RequestContext) request.GET.get(‘param1’, None) in the view.
this line of code at = AttachedInfo.objects.filter(attachedMarker=m.id, title=title) returns a queryset and you are trying to access a field of it (that does not exist). what you probably need is at = AttachedInfo.objects.get(attachedMarker=m.id, title=title)
You can use the request object to find the logged in user def my_view(request): username = None if request.user.is_authenticated(): username = request.user.username According to https://docs.djangoproject.com/en/2.0/releases/1.10/ In version Django 2.0 the syntax has changed to request.user.is_authenticated