On Sep 26, 2008, at 2:56 PM, [EMAIL PROTECTED] wrote:
> > hmm. the joins are ... hard to generate, especialy in proper/sensible > combinations. (i've nearly given up on pushing further my > python-expression-to-sa converter, the logic fails on 1/3 of the > a.b.c join-cases.) sorry you've given up, but welcome to SQLAlchemy's original philosophy ! :) > And especialy if there is OR involved... (these damned ORs -:) > As there's no filter_or(), i was thinking i'll be able to do > generatively > myfilter = some.thing.has(this) | some.otherthing.any(that) & .. > then query.filter( myfilter) > but seems that's still in unforeseeable __future__ > if the any/has/... can nest subselects, cant that be made somehow more > levels? sa sure knows all that is needed to make that.. if you wanted to add more doodads to has()/any() you could approach that with a comparator_factory to start with. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
