Thanks for your comment!
Relying on another ORM isn't technically necessary, but it seems to me
the easiest way - instead of issuing select statements, the generated
code looks like this:
for s in src.myapp.City.select():
d = dst.myapp.City()
d.id = s.id
d.name = s.name
d.save()
Using select statements, the code would have been much uglier, and
much harder to modify, I think.
Noam
On Jul 18, 4:36 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 7/17/07, Noam Raphael <[EMAIL PROTECTED]> wrote:
>
> > I would really like to hear what you think about it (especially if
> > it's good things...) Tell me!
>
> I haven't looked at the code, but I wonder about the dependency on
> multiple ORMs; the Django ORM cannot expose its own functionality on
> multiple databases at once, but this does not mean you cannot have
> connections open to multiple databases at once -- if you have the
> location and credentials for the second connection, you can simply
> drop down to the database adapter module, open a new connection
> independently of Django and use the standard Python DB API to execute
> any SQL you like.
>
> So unless you're relying heavily on ORM methods to access the data,
> instead of using simple SELECT statements, there's not any technical
> need to install another ORM package.
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
