I am planning an external package to assist my developers in getting their 
special-purpose DDL out of the database and into git.   Some teams can 
handle it, but some teams could use help making sure that they use 
operations.RunSQL well and wisely.

My biggest questions about what I'm doing are:
* Are there any packages that already attempt to do what I'm thinking of?
* What gotchas have I not considered?
* What should it be called?   What should the management command be called?
* How do I test it well?

Here is a more detailed idea of the packages key contributions (
https://github.com/danizen/django-sqlextras/):

* Create a migration operation that is a subclass of RunSQL, but takes a 
forward object that consists of a path and an expected checksum, and a 
similar optional backwards checksum.
* Create a management command that can build migrations using this 
operation (or you can do it yourself, of course).

Feedback is welcome.

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/73a56671-3904-4eef-b82a-d04fe175c993%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to