Hi Chris, On 10/22/2014 09:05 AM, Chris Foresman wrote: > Good points. I went looking for `callproc()` documentation and couldn't > find anything useful, which if I understand correctly is part of the > reason this thread started. So +1 on documenting it! > > The most complicated part of dealing with store procedures from a high > level is getting them in the database to begin with, and updating them > if they need to change. Obviously I'm just manually entering them via > the console, but it would be great if there was some consistent way to > add them to the database via Migrations or something similar.
As Marc suggested, I think migrations do already solve this problem, via the RunSQL operation. (It doesn't offer any abstraction over writing the stored procedure, but I'm not sure what kind of abstraction would be useful there. It does provide a place to put it that ensures it will get run on every database - though previously you could use initial SQL for that purpose.) Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5447D059.2060302%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
