just curious, if you don't type "cte()", you have just a selectable. From a Python perspective it should work exactly the same way (e.g. CTEs are a SQL syntactical trick that SQLAlchemy to some degree provides already in Python, at least semantically). Is there something other than performance / SQL complexity that changes?
I'd have to find time to look at this as with CTE/union it's probably a crapshow, and I'm sort of overloaded with those right now.... On Sep 25, 2014, at 9:12 PM, Jonathan Vanasco <jvana...@gmail.com> wrote: > This is the test case I've been working on today. > > https://gist.github.com/jvanasco/9be1f528526e496fc751 > > The target sql looks crappy, because it's just an example. > > the various issues have been: > > * if i can build a query without an Exception: > ** I duplicate the query within a subqueries > ** I build it in a way that I don't have addressable columns (for > sorting/joins/etc) > > * if i raise an exception (more often), it's because I'm not able to turn a > union/cte into the correct type of object (which has addressable columns, etc) > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
