convore.json/groups/django-community/using-south-with-django-13-and-multiple-databases/messages.json

[{"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1301997213.936775, "message": "I've been trying to do that without much luck. Seems that South simply does not respect the database router.", "group_id": 81, "id": 539490}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1301997225.7664199, "message": "Using the latest stable build 0.7.3.", "group_id": 81, "id": 539491}, {"user_id": 8740, "stars": [{"date_created": 1302022254.5300469, "user_id": 1822}], "topic_id": 17358, "date_created": 1302022237.762085, "message": "@ptone No, as we're still working them out. I'll get a 0.7.4 release out soonish once everything appears to work", "group_id": 81, "id": 543300}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302022254.897007, "message": "FTR, I've been using South with 1.3 for the past few months as it develops, so it's not that far off", "group_id": 81, "id": 543304}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302021932.2528059, "message": "0.7.3 isn't 1.3 compatible in a few respects; there's already a few fixes in the trunk version, so I'd try that first.", "group_id": 81, "id": 543251}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302022337.0273149, "message": "@ptone Hey, it started out small. And yes, not entirely, though it is suffering slightly", "group_id": 81, "id": 543313}, {"user_id": 1822, "stars": [], "topic_id": 17358, "date_created": 1302022205.10992, "message": "@andrewgodwin Is there any place where these incompatibilities are listed in summary form?", "group_id": 81, "id": 543297}, {"user_id": 1822, "stars": [], "topic_id": 17358, "date_created": 1302022290.6192601, "message": "glad to see your new *ahem* small project isn't taking you entirely away from South", "group_id": 81, "id": 543306}, {"user_id": 8740, "stars": [{"date_created": 1302022366.3418789, "user_id": 1822}], "topic_id": 17358, "date_created": 1302022358.219697, "message": "though I'll be doing a lot more work over the summer, and possibly have a GSOC student working on some Django-related stuff for it, we'll see", "group_id": 81, "id": 543314}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302071058.485101, "message": "@andrewgodwin thanks. Is there a good support for multiple databases?  BTW, do I need the south migration table in all the databases?", "group_id": 81, "id": 555361}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081520.0318949, "message": "@zvikico There isn't \"good support\", no - much like Django, there's a basic level there you need to build on, as every multi-db setup is different.", "group_id": 81, "id": 557182}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081832.970392, "message": "then you're starting to fall out of South's 90% remit :)", "group_id": 81, "id": 557208}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081694.45805, "message": "Well, if you want to create the table in the correct database, there's an allow_syncdb method for that.", "group_id": 81, "id": 557196}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081708.7236731, "message": "You shouldn't be creating it in all the databases.", "group_id": 81, "id": 557197}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081592.0161021, "message": "Well, I have a database router which I wrote, and django works fine.", "group_id": 81, "id": 557190}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081786.377254, "message": "I've got more than two databases...", "group_id": 81, "id": 557205}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081566.837991, "message": "and, IIRC, you only need a south history table in the default DB", "group_id": 81, "id": 557186}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302082037.91133, "message": "Well, database routers...", "group_id": 81, "id": 557221}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081740.624572, "message": "it takes models, not table names", "group_id": 81, "id": 557201}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081916.145112, "message": "Sounds reasonable.", "group_id": 81, "id": 557212}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302082097.597779, "message": "Anyway, thank you for the information.", "group_id": 81, "id": 557222}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081618.0190489, "message": "yeah, the database router is you building on Django :)", "group_id": 81, "id": 557192}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081555.623554, "message": "You can tell South which database to run against using --database, but it will apply the same migrations and make the same tables in each one", "group_id": 81, "id": 557184}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081616.921298, "message": "That's really not how Django is working.", "group_id": 81, "id": 557191}, {"user_id": 8740, "stars": [{"date_created": 1307626783.3964341, "user_id": 3756}], "topic_id": 17358, "date_created": 1302081713.052443, "message": "if you've got different tables in different databases, you're best off having two separate migration sets and wrapping South's migration commands to change SOUTH_MIGRATION_MODULES", "group_id": 81, "id": 557198}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081721.733263, "message": "no, allow_syncdb does not work for South", "group_id": 81, "id": 557200}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081881.7480819, "message": "we _could_ support a whole new function or two on database routers, but that would require significant work and remodelling of some of the core", "group_id": 81, "id": 557210}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081891.3514891, "message": "and there's plenty of other things that need doing that affect more people", "group_id": 81, "id": 557211}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081942.6092391, "message": "you can always use the internal parts of South more directly; you can manually tell it to run single migrations, for example", "group_id": 81, "id": 557215}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302081956.2413869, "message": "but autodetection is going to get very confused", "group_id": 81, "id": 557216}, {"user_id": 11827, "stars": [], "topic_id": 17358, "date_created": 1302081957.3597081, "message": "It's not very clear from the documentation, though. It should be clearly stated that the multi-db is simply not supported.", "group_id": 81, "id": 557217}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302082006.9982369, "message": "it is, if you use it in the other ways", "group_id": 81, "id": 557219}, {"user_id": 8740, "stars": [], "topic_id": 17358, "date_created": 1302082012.842716, "message": "e.g. master/slave read/write mode", "group_id": 81, "id": 557220}, {"user_id": 3756, "stars": [], "topic_id": 17358, "date_created": 1307626887.331491, "message": "@andrewgodwin Thanks a lot for that tip! I had the same requirement and wrapping South's migration to change SOUTH_MIGRATION_MODULES worked like a charm, it even works when running tests!", "group_id": 81, "id": 1350142}, {"user_id": 25337, "stars": [], "topic_id": 17358, "date_created": 1308047372.2427399, "message": "fwiw - I'm using South dev version on a large 1.3 project (with lots of dynamically generated models, no less) with few problems. Another release soon would be cool though :)", "group_id": 81, "id": 1389805}, {"user_id": 25337, "stars": [], "topic_id": 17358, "date_created": 1308047391.6215999, "message": "Single database though, so totally OT for the thread, I've just realised - sorry! :)", "group_id": 81, "id": 1389810}]