In my specific case, I have two kinds of "messages" that I need to retrive and paginate.
Let's omit the details, and just say that the first kind is in a model called Msg1 and the other is called Msg2
The fields of these two models are completely different, the only fields that are common to the two models are "date" and "title" (and of course, id).
I can get Msg1.objects.all()
and Msg2.objects.all()
but can I combine these two queries into one query, sort it by date, and paginate it?
I need to preserve the lazy nature of the query.
The trivial solution is to list(query)
both queries and combine them in a python list. but this is inefficient for obvious reasons.
I looked through the django references on models and dp-api, but it doesn't seem that there is a way to combine queries of different models/tables into one.
1 Answer. Show activity on this post. In your models Device and History models are related with a foreign key from History to DeviceModel, this mean when you have a History object you can retrieve the Device model related to it, and viceversa (if you have a Device you can get its History).
Django-filter is a generic, reusable application to alleviate writing some of the more mundane bits of view code. Specifically, it allows users to filter down a queryset based on a model's fields, displaying the form to let them do this. Adding a FilterSet with filterset_class. Using the filterset_fields shortcut.
A QuerySet is a collection of data from a database. A QuerySet is built up as a list of objects. QuerySets makes it easier to get the data you actually need, by allowing you to filter and order the data.
I would suggest that you use Model inheritance.
Create a base model that contains date and title. Subclass Msg1 and Msg2 off it as described. Do all your queries (to fill a page) using the base model and then switch to the derived type at the last moment.
The really great thing about inheritance is that django then allows you to use the base model in foreign keys from other models, so you can make your whole application more flexible. Under the hood it is just a table for the base model with a table per sub-model containing one-to-one keys.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With