“You can use a @property so that when you get back an A or a B object , they
seek to return either the column on A or the column on B.“
I believe you’re describing the behavior I currently have, I.e. if I query B
then I can get b.visible_id otherwise I get A.visible_id.
I see your point about
On Fri, Feb 14, 2020, at 12:35 PM, Mark Aquino wrote:
> I have a polymorphic class structure like this, with a lot of classes
> extending the parent class.
> In reality I'm using a Mixin that declares the visible_id column and it's
> defined with @declared_attr.cascading, but for simplicity:
If AWS lambda doesn't offer any kind of stepwise debugging facility then you
would have to keep trying different things, differnet combinations of
configuration / imports, and whatever else you can think of that makes the
behavior occur or not occur, until you can isolate it to a single thing.
