> >> assert t.compare(t2)
> >
> > yes i was hoping for such method (:-)
> > And the best will be if it can produce a list/ hierarchy of
> > differences, which then programaticaly can be iterated - and
> > checked and resolved or raised higher.
> >
> >> but why not just use autoload=True across the board in the first
> >> place and eliminate the chance of any errors ?
> >
> > what do u mean? The db-model of the app will not be the db-model
> > in the database - and the semantix will be gone.
> > Example:
> >  from simplistic renaming of columns/ tables, to splitting a
> > class into clas+subclass (table into 2 joined-tables) etc
>
> ok, fine.  anyway, feel free to add a trac ticket for this one -
> it'll need a volunteer.
ticket #680, have a look if what i wrote is what was meant in this 
thread.
i may look into it after 2-3 weeks - unless someone does it ahead of 
me ;P)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to