On Apr 13, 5:06 pm, Craig Lucas <craigmlu...@gmail.com> wrote: > I can attempt to merge his changes in and test it. Do people typically > merge these changes in manually? I see changes from a bunch of different > people over the last 4 years, should I just grab the last guys changes?
The most recent work can be found from here: <https://github.com/ akaariai/django/tree/schemas>. Unfortunately that branch has been a bit volatile recently, and I do not recall how well the tip of that branch works. I will try to clear it up a little and add a patch to Trac for easier testing. In general supporting db schemas isn't that complicated from query generation perspective, but it adds a lot of code to database creation and especially into introspection. Introspection and database creation support is critical, as Django's test runner relies on these features. After a little cleanup the branch should be ready for some feature testing, but it definitely isn't ready for production use yet. However, if you (or somebody else) has time to just test if the feature works for your use case, that information would be very valuable. There is the question if we want to add full support for database schemas. My opinion is unsurprisingly yes, as otherwise I would not work on this feature. However, at the moment this feature adds around 1000 lines of code, most of it is to backends. I guess that South for example will need a lot of changes to its introspection methods to have working schema support. Other external projects that deal with table names directly (either raw SQL or otherwise) will need to be updated, too. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
