Build a dynamic filtering form with Django // 6 - Filtering by date and view count
ฝัง
- เผยแพร่เมื่อ 7 เม.ย. 2019
- In this project we teach how to build a dynamic form for filtering your Django models. In this video we start filtering by date and view count.
justdjango.com
☝ Get exclusive courses & become a better Django developer
💻 Project code: github.com/justdjango/djfilter
✌️ Stay in touch
Facebook: / justdjangocode
Instagram: / justdjangocode
Twitter: / justdjangocode
Email: admin@justdjango.com
Thank you for watching and don't forget to subscribe :)
You saved my college assignment and mental health thank you!!
That's awesome video! I am learning Django for more than a year and still I found something new in this channel. In this vid I found out I can use "cascaded" filter on ORM object - I can filter the object again and again.
really good django tutorial
Hey man... thanks for all you do, and keep up the great work! Much appreciated!!!
훌륭한 강의입니다! Great Tutorial!
Awesome video!!
You are a godsend
Thank you very much for this series. I have just about come to terms with Django and could not find how to handle dynamic filters.
AWESOME.
awesome
Thanks!
GREAT
Hi ! Awesome video thank you. Do you think it's possible to do the same thing with tables ?
Cooll
how can I pass the values back to the template so the user can see which filters are applied?
up
Thank you for this series. But I am curious: why didn’t you use DateTimeRangeField and or IntegerRangeField?
Nice! By querying all and then filtering, are fetching too much? or are we querying multiple times?
Great video again. One question - how do you do the 'entering two lines at once' editing in VSCode? I can't even think of what to search for to find out how to do it.
On Mac you place the cursor and then hold the option key while clicking to place the cursor in the next place. On Windows I think it would be the alt key
On linux it's Alt + left mouse or Ctr + Shift + arrow(up/down)
Wait, am I correct in thinking the mechanism here is to fetch all the table’s rows into memory and then filtering that down to only what you want? No problem if it’s a small table but not very viable if it had millions of rows. I suppose you could compose Django Q objects into a tuple and then ‘Journal.objects.get(*tuple_q)‘ so most of the code would still apply.
There is nothing being stored in memory. This explains how querysets are evaluated: docs.djangoproject.com/en/2.2/ref/models/querysets/#when-querysets-are-evaluated
Great job! How can I support you?
Hi can this be used off model methods aswell?
what if the category was a multiSelectField?
Hi while using the Date Filter, it does not work and in the terminal I get an error saying : RuntimeWarning: DateTimeField TwitterL4.trend_start_time received a naive datetime (2019-05-14 00:00:00) while time zone support is active. How to resolve this
Hey, it's like 9 months later, so I don't know if you still need an answer or not, but basically there are two kinds of time: 'naive', and 'timezone'. So timezone should be obvious, and naive is a time without time zone information. In your settings you are using timezone (it might just say 'tz') but the code is time naive, which is why you got this error. Look up time and time zone in the Django docs for more info.
{% empty %}
No results found