Of course! Thanks for the quick reply, I was afraid/hoping it would be
something simple I was missing -- I wasn't aware that it was required on
both sides of a bi-directional relationship, but that makes sense. I'm
using 1.3.17 and it does the same, I just only copied the first part of the
hi and thanks for the straightforward test case.
I'm not sure if that's an old version of SQLAlchemy you're using, when I run
with current 1.3.18 release the error message is more descriptive:
"Could not determine join condition between parent/child tables on relationship
ACollection.members -
I have SQLA classes in a project that have date and data components and I'm
attempting to create a single base-class that I can subclass to create
statistics for all points of data during some interval, but I want the
interval subclasses to maintain references to their sub-data such that if I