Hey all, GSOC is officially scheduled to start tomorrow (my time), however I've take the liberty of getting quite a jump on my work (as I described last week). During this week I got the save using parameter and using queryset method, these are fairly untested however. The reason for this was after updating the management commands and testing harness for multiple database support any fixtures being loaded would be loaded N time (where N is the number of dbs in your settings.DATABASES setting), so I needed to make sure each fixture got loaded into each DB, this meant adding the using parameter to save, which also uses querysets... and it was turtles all the way down :)
So while that's basically working, the test suite as a whole is still not passing (http://paste.pocoo.org/show/118532/ is the results for me). The reason for this (as best I can tell) is that Postgresql runs DDL operations inside a transaction, and since transaction support isn't actually working across DB at this point the CREATE TABLE statements never actually get committed. Which brings us to the problem: updating the transaction stuff in itself isn't a huge task, and making django use transaction stuff where necessary isn't tremendously onerous. However, one of -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
