I just installed the multi-db branch yesterday and I think it is something that surely must be supported, and I'll play more with it the coming time. I have a simple schema-evolution idea that does not alter existing tables, but simply copies data to new tables in another database. Don't know if somebody is working on that, but it's a nice way for me to dive into some code :-)
Anyway, one problem with multi-db immediately popped up: you cannot have duplicate model names, which kind of kills the schema-evolution idea... I've tracked it down to the ModelMeta class that does a check on the class name, I'll have a look to see if that can be altered without breaking anything. Thanks for all the work on the multi-db branch, I hope it gets merged! Ciao, Marc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
