On Sun, Jul 19, 2009 at 3:29 PM, Jon Loyens<jonloy...@gmail.com> wrote: > > Hi everyone (particularly those working on multidb), > > I have a pretty simple use case that involves use of multidb support > and I was wondering if the code base for multidb is far enough along > to help me out on this. Basically, I have a legacy enterprise db that > I've created working models for using inspectdb. The models work and > are a big help in navigating and retrieving the data. > > What I need to do now is transform some of the data and then store the > data in a new set of models in a different database. Of course I > could just open another connection using mysqldb and just write raw > sql but what would be great is if I could use the django ORM to > manipulate the data from the first database and then store it in the > second. > > My question is this: is there enough work done on multi-db already > that maybe with maybe a little hack or two I could accomplish this? > > JL > > >
Assuming that you're legacy DB doesn't use a custom Query class (meaning it's not Oracle or one of the external backends), then multi-db should easily be able to do what you want, check the docs the multiple_database regression tests for a sense of the API. (Remember to use the soc2009/multidb branch, not the old multi-db one). Alex -- "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 "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
