On 7/18/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> Just out of interest have you explored using SQLAlchemy directly with the
> django model..? I mean mapping the SA Table onto the django Model..? I had a
> play with that a while back and it seems a very straightforward way of
> achieving SA - dj
Just out of interest have you explored using SQLAlchemy directly with the
django model..? I mean mapping the SA Table onto the django Model..? I had a
play with that a while back and it seems a very straightforward way of
achieving SA - django integration...
Ben
On 18/07/07, Noam <[EMAIL PROTECTED
On Jul 18, 4:47 am, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> > 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...
>
> It can using the multiple-db-support branch (see ticket 47
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.na
> 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...
It can using the multiple-db-support branch (see ticket 4747 for a patch
bringing the branch up to date)... There's also a si
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
6 matches
Mail list logo
