Re: [sqlalchemy] meta.sorted_tables exception with 0.6.3

2010-09-07 Thread werner
Michael, On 06/09/2010 19:42, Michael Bayer wrote: On Sep 6, 2010, at 1:23 PM, werner wrote: Michael, Thanks for the fast reply. On 06/09/2010 15:53, Michael Bayer wrote: engine = create_engine(...) m = MetaData() t = Table('foo', m, autoload=True, autoload_with=engine) #<--- boom The

Re: [sqlalchemy] meta.sorted_tables exception with 0.6.3

2010-09-06 Thread Michael Bayer
On Sep 6, 2010, at 1:23 PM, werner wrote: > Michael, > > Thanks for the fast reply. > > On 06/09/2010 15:53, Michael Bayer wrote: >> engine = create_engine(...) >> >> m = MetaData() >> t = Table('foo', m, autoload=True, autoload_with=engine) #<--- boom > The table which errors has the follow

Re: [sqlalchemy] meta.sorted_tables exception with 0.6.3

2010-09-06 Thread werner
Michael, Thanks for the fast reply. On 06/09/2010 15:53, Michael Bayer wrote: engine = create_engine(...) m = MetaData() t = Table('foo', m, autoload=True, autoload_with=engine) #<--- boom The table which errors has the following definition. It seems to have to do with the two columns MIN

Re: [sqlalchemy] meta.sorted_tables exception with 0.6.3

2010-09-06 Thread Michael Bayer
This issue is not related to sorted_tables and is a failing assertion within Firebird reflection code. The rdb$relation_fields view is returning an unexpected value.The code in 0.5 is pretty much the same thing though so not sure how something different is occuring. You'd need to provide

[sqlalchemy] meta.sorted_tables exception with 0.6.3

2010-09-06 Thread werner
I am writing a bit of code to dump data from one db into another one. Basic structure of the db's are the same, one is in FB 2.1 format and the other other in FB 2.5 format and all primary keys are BIGINT instead of INTEGER. I am still on 0.5.8 and using "reversed(meta.sorted_tables)" doesn