http://www.chrisumbel.com/article/django_python_stored_procedures.aspx Comments about Stored Procedures in Django from the blog of Chris Umbel, software developer and database administrator. 2009-08-09 18:08:37 UTC http://www.chrisumbel.com/article/django_python_stored_procedures.aspx#comment_4c4b2ecf9453131804000021 Darn close. In my case I'm conditionally performing some write operations via other procedures (essentially logging and transaction tracking) in a third-party second database /* if some condition is met */ call OtherDatabase.LogSearch(...); and conditionally union-ing my query results with a table in that second database; /* if some condition is met */ select title, url from searcher_document union select title, url from OtherDatabase.documents; It's a definite edge-case. http://www.chrisumbel.com/article/django_python_stored_procedures.aspx#comment_4c4b2ecf9453131804000021 2009-08-10T16:08:19+00:00 http://www.chrisumbel.com/article/django_python_stored_procedures.aspx#comment_4c4b2ecf9453131804000020 Do you have an example of where you can't avoid stored procs? I can't think of any except when your using a shared-db legacy application, which is not the case when your using Django. http://www.chrisumbel.com/article/django_python_stored_procedures.aspx#comment_4c4b2ecf9453131804000020 2009-08-10T14:08:11+00:00