Performance difference between django query and stored procedure (MySQL)?

[Maor Levy]

I was wondering what the performance hit on using a django query over a stored procedure would be? I realize that django doesn't support stored procedures so that's why I was hoping to avoid using stored procedures. However, then the query won't be compiled in the db and the calculations would have to be done in python ... etc. What's the difference in performance between a django query and a store procedure called from django?

[Sergiy Khohlov]

better way is using storing procedure.

You  also can compare trivial SQL command and stored procedure performance.  Result is a same  such as django and stored procedure (or near to the same) 

Many thanks,

Serge


+380 636150445
skype: skhohlov

On Fri, Jan 8, 2016 at 4:30 PM, Maor Levy <maor...@gmail.com> wrote:

I was wondering what the performance hit on using a django query over a stored procedure would be? I realize that django doesn't support stored procedures so that's why I was hoping to avoid using stored procedures. However, then the query won't be compiled in the db and the calculations would have to be done in python ... etc. What's the difference in performance between a django query and a store procedure called from django?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/58776ba6-c4de-4110-92f2-6f915e4a7e38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.