Thanks for the reply, Mike. In that case, I'll just keep a copy of our
definitions in the test case folder and correct them whenever required.
Hopefully, these will get merged to the real code sooner or later (which is
why I wanted to name it backlogs).
The goal is to stage tables(which are requir
I dont think there's an obvious way to override declarative classes like that,
but I also dont understand the problem such that something like that would be
necessary (that is, I dont understand why you need "create tables on the fly",
is this in a local testing database where you *do* create ta
We use SQLAlchemy to read/write data, but not create tables (as it done by
DBAs). Due to this, some of the definitions which are incorrect, have not
yet been caught (though it works for reads/writes etc.).
Is there a DRY way to to override them for testing purposes (create tables
on the fly etc