Re: Background Programs in Django

[Tiago Albineli Motta]

Create a django command to do the job and put it in the crontab


On Wednesday, September 26, 2012 9:07:23 AM UTC-3, surya wrote:
>
> I have to use RSS/ Atom feeds of blogs in my Django app. So, I thought to 
> use Google Feed API. All the API provides is a BIG list of feeds..
>
> If I need a post (say no 25), I need to GET the whole feeds and search 
> every time which is redundant. *So, I am thinking to run a background 
> program which periodically performs GET and updates the feeds as a JSON 
> file. Now, I can at least do some work efficiently!*
> *
> *
> If anyone got a better idea, please do tell me.
>
> Can anyone tell me how to do that? It should be in sync with requests I 
> perform on the JSON file in Django..
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/ISao-2E164cJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: A lots of foreign keys - Django Admin

[Tiago Albineli Motta]

We had similar problem a few months ago, one join in only two tables (but 
those two tables were big, very big) we solve the problem denormalizing the 
table. So everytime we save some row for table1, we update the table2 with 
a column table1_name_cache. In the list, we display this column.
 

On Wednesday, September 26, 2012 11:16:29 AM UTC-3, rentgeeen wrote:
>
> Here is mysql profiling:
>
> Results:
>
> Query:
>
> http://cl.ly/image/0311392u0Z0S
>
> CPU Profile:
>
> http://cl.ly/image/2D210h0f1L06
>
> On Wednesday, 26 September 2012 09:38:03 UTC-4, rentgeeen wrote:
>>
>> If you want I can send you a zip of the project 
>>
>> On Wednesday, 26 September 2012 09:34:33 UTC-4, rentgeeen wrote:
>>>
>>> Here is the SQL again it overlap in previous post dont know why it 
>>> posted twice:
>>>
>>> *SELECT* `auto_type`.`id`, `auto_type`.`client_id`, 
>>> `auto_type`.`category_id`, `auto_type`.`subcategory_id`, 
>>> `auto_type`.`project_id`, `auto_type`.`title`, `auto_client`.`id`, 
>>> `auto_client`.`title`, `auto_category`.`id`, `auto_category`.`client_id`, 
>>> `auto_category`.`title`, T4.`id`, T4.`title`, `auto_subcategory`.`id`, 
>>> `auto_subcategory`.`client_id`, `auto_subcategory`.`category_id`, 
>>> `auto_subcategory`.`title`, T6.`id`, T6.`title`, T7.`id`, T7.`client_id`, 
>>> T7.`title`, T8.`id`, T8.`title`, `auto_project`.`id`, 
>>> `auto_project`.`client_id`, `auto_project`.`category_id`, 
>>> `auto_project`.`subcategory_id`, `auto_project`.`title`, T10.`id`, 
>>> T10.`title`, T11.`id`, T11.`client_id`, T11.`title`, T12.`id`, T12.`title`, 
>>> T13.`id`, T13.`client_id`, T13.`category_id`, T13.`title`, T14.`id`, 
>>> T14.`title`, T15.`id`, T15.`client_id`, T15.`title`, T16.`id`, T16.`title`
>>>  *FROM* `auto_type` *INNER JOIN* `auto_client` *ON* 
>>> (`auto_type`.`client_id` 
>>> = `auto_client`.`id`) *INNER JOIN* `auto_category` 
>>> *ON*(`auto_type`.`category_id` 
>>> = `auto_category`.`id`) *INNER JOIN* `auto_client` T4 *ON* 
>>> (`auto_category`.`client_id` 
>>> = T4.`id`) *INNER JOIN* `auto_subcategory` 
>>> *ON*(`auto_type`.`subcategory_id` 
>>> = `auto_subcategory`.`id`) *INNER JOIN* `auto_client` T6 *ON* 
>>> (`auto_subcategory`.`client_id` 
>>> = T6.`id`) *INNER JOIN*`auto_category` T7 *ON* 
>>> (`auto_subcategory`.`category_id` 
>>> = T7.`id`) *INNER JOIN* `auto_client` T8 *ON* (T7.`client_id` = 
>>> T8.`id`) *INNER JOIN* `auto_project` *ON*(`auto_type`.`project_id` = 
>>> `auto_project`.`id`) *INNER JOIN* `auto_client` T10 *ON* 
>>> (`auto_project`.`client_id` 
>>> = T10.`id`) *INNER JOIN* `auto_category` T11 
>>> *ON*(`auto_project`.`category_id` 
>>> = T11.`id`) *INNER JOIN* `auto_client` T12 *ON* (T11.`client_id` = 
>>> T12.`id`) *INNER JOIN* `auto_subcategory` T13 
>>> *ON*(`auto_project`.`subcategory_id` 
>>> = T13.`id`) *INNER JOIN* `auto_client` T14 *ON* (T13.`client_id` = 
>>> T14.`id`) *INNER JOIN* `auto_category` T15 *ON*(T13.`category_id` = 
>>> T15.`id`) *INNER JOIN* `auto_client` T16 *ON* (T15.`client_id` = 
>>> T16.`id`) *ORDER* *BY* `auto_type`.`id` *DESC*
>>> *
>>> *
>>> *below are screenshots
>>> *
>>> On Wednesday, 26 September 2012 09:33:02 UTC-4, rentgeeen wrote:

 I am sorry I post the old one here is the update:

 Screenshot:

 http://cl.ly/image/2A3z1q2l053l

 Screenshot of Admin clicking on TYPES = 60 seconds to load this is the 
 query

 http://cl.ly/image/1G1S0c0r302s

 if I remove from admin "list_display

 class ProjectAdmin(admin.ModelAdmin):

 list_display = ('client', 'category', 'subcategory', 'title', )

 admin.site.register(Project, ProjectAdmin)

 all foreign keys then in admin all works super fast.


 *SELECT* `auto_type`.`id`, `auto_type`.`client_id`, 
 `auto_type`.`category_id`, `auto_type`.`subcategory_id`, 
 `auto_type`.`project_id`, `auto_type`.`title`, `auto_client`.`id`, 
 `auto_client`.`title`, `auto_category`.`id`, `auto_category`.`client_id`, 
 `auto_category`.`title`, T4.`id`, T4.`title`, `auto_subcategory`.`id`, 
 `auto_subcategory`.`client_id`, `auto_subcategory`.`category_id`, 
 `auto_subcategory`.`title`, T6.`id`, T6.`title`, T7.`id`, T7.`client_id`, 
 T7.`title`, T8.`id`, T8.`title`, `auto_project`.`id`, 
 `auto_project`.`client_id`, `auto_project`.`category_id`, 
 `auto_project`.`subcategory_id`, `auto_project`.`title`, T10.`id`, 
 T10.`title`, T11.`id`, T11.`client_id`, T11.`title`, T12.`id`, 
 T12.`title`, 
 T13.`id`, T13.`client_id`, T13.`category_id`, T13.`title`, T14.`id`, 
 T14.`title`, T15.`id`, T15.`client_id`, T15.`title`, T16.`id`, T16.`title`
  *FROM* `auto_type` *INNER JOIN* `auto_client` *ON* 
 (`auto_type`.`client_id` 
 = `auto_client`.`id`) *INNER JOIN* `auto_category` 
 *ON*(`auto_type`.`category_id` 
 = `auto_category`.`id`) *INNER JOIN* `auto_client` T4 *ON* 
 (`auto_category`.`client_id` 
 = T4.`id`) *INNER JOIN* `auto_subcategory`