On 6/30/14, 6:01 PM, univerio wrote:
Consider the following configuration:
class Employee(Base):
__tablename__ = employee
id = Column(Integer, primary_key=True)
type = Column(String(100))
cars = relationship(Car)
__mapper_args__ = {
On 6/30/14, 7:03 PM, Mike Bayer wrote:
there's a little bit of a glitch here, however in any case, the ORDER
BY would be from E.Engineer.specialty.
The glitch is that the subq load at the moment seems to need an
additional hint as to what its selecting from:
Thanks for the quick response, Mike!
On Mon, Jun 30, 2014 at 4:26 PM, Mike Bayer mike...@zzzcomputing.com
wrote:
On 6/30/14, 7:03 PM, Mike Bayer wrote:
there's a little bit of a glitch here, however in any case, the ORDER BY
would be from E.Engineer.specialty.
The glitch is that the
On 6/30/14, 7:29 PM, Jack Zhou wrote:
Thanks for the quick response, Mike!
that's all fixed in master / rel_1_0 and rel_0_9 branches (as you know I
like to fix these deep polymorphic loader issues ASAP)
On Mon, Jun 30, 2014 at 4:26 PM, Mike Bayer mike...@zzzcomputing.com
