ive identified this specific issue and fixed it; it has to do with
overriding primary key columns that are reflected (the
PrimaryKeyConstraint got two versions of the same column in it, one
of which was not in the table's main collection of columns, which is
an invalid state). it is fixed
the error that seems to be popular this week is related to people
trying to add foreign keys to reflected tables; we dont have unit
tests set up for this yet so its likely that the tables are getting
conflicting column objects set up. the reason it probably doesnt
work at the table reflect
2 matches
Mail list logo
