Re: Issues and Improvements to the The Django Administration

2020-12-16 Thread Muskan Vaswan
On Dec 16, 2020, at 2:17 PM, Carles Pina i Estany wrote: My message is that it probably can be done without COUNT if need to be and show "more than X rows" instead of the exact number of rows. Well yes this makes sense to me now, but only in the sense that we would first check whether some

Re: Issues and Improvements to the The Django Administration

2020-12-16 Thread Carles Pina i Estany
Hi, On Dec/16/2020, Muskan Vaswan wrote: > Carles Pina I Estany: While I understand what you’re trying to do I > don’t know why we are trying to avoid COUNT is there a best practice > associated with this that I don’t know about? We are (or... I was :-) ) trying to answer this question as

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Muskan Vaswan
The point is that there is a way, in fact multiple ways that this could be implemented without changing the models. A change to the method I suggested in my last mail would be to avoid looping over the query set at all or even the Entry() class and using values and the the Count() annotation in

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Akshat Sharma
Hi Well I am an webdevloper and pretty new to the django so but If the issue is only to make log more efficient and useful then we can implement javascript into the admin site it can be resolved with pretty simple js and can be directly implemented into HTML and can be a major advantage in

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Carles Pina i Estany
Hi, On Dec/16/2020, Muskan Vaswan wrote: > LogEntry which are used in the templates already. Note that this is the > most basic draft just to give an idea of what I’m trying to say. About > having 1000 rows, we will have to reach a consensus to put an upper limit > to the number of rows that

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Muskan Vaswan
1. Agreeably this won’t be easy but I might have a way of doing this without having to make changes to the data model. We can leave the data model as it is but manipulate the context that we give to by changing the simple query (Line 16

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Adam Johnson
> > I would suggest something like 50 or 100. Let me know what you think, and > if I made any sense at all But in this case, we might show something like "User X deleted 50 rows", when really they deleted 1000. I don't think we'd want to show such an inaccurate message. If you want though, you

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Muskan Vaswan
1. Agreeably this won’t be easy but I might have a way of doing this without having to make changes to the data model. We can leave the data model as it is but manipulate the context that we give to by changing the simple query (Line 16

Re: Issues and Improvements to the The Django Administration

2020-12-15 Thread Muskan Vaswan
[image: WhatsApp Image 2020-12-15 at 10.55.37 PM.jpeg] On Wednesday, 16 December 2020 at 00:12:40 UTC+5:30 Muskan Vaswan wrote: > I have the following suggestions and issues with the Django site > administration: > > 1. When deleting or adding items in Bulk (especially deleting), The Recent >

Issues and Improvements to the The Django Administration

2020-12-15 Thread Muskan Vaswan
I have the following suggestions and issues with the Django site administration: 1. When deleting or adding items in Bulk (especially deleting), The Recent Actions should show “Deleted 15 Items” rather than every deleted item singularly which just occupies space and doesn't make a lot of sense