On Jul 26, 4:59 pm, nixlists <nixmli...@gmail.com> wrote: > On Tue, Jul 26, 2011 at 7:42 AM, Roman Klesel<roman.kle...@googlemail.com> > wrote: > > ... > > > The main question you may ask yourself may be whether or not you > > really want to have django do the whole calculation thing. Many > > database engines have very powerful aggregation capabilities, support > > for stored procedures, functions etc. > > Some of the aggregation features are available through the django orm. > > Thanks, > > Is it a best practice to take a bunch of code out to the stored > procedures as much as possible, or the opposite is true with Django?
It all depends on your project's requirements. A generic app should be as db-agnostic as possible (that is, should work on any DB you can use with Django), which may make stored procs somewhat unpractical. If it's a specific, custom app and the specs says "it will run on this exact DB, period", then stored procs may be fine (just make sure the customer / DBA is ok...). This being said, you can already do a lot with standard SQL functions and aggregation. -- You received this message because you are subscribed to the Google Groups "Django users" group. 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.
