I've added a PR for full=True in outerjoin(), join() and Join():
https://github.com/zzzeek/sqlalchemy/pull/167
FULL OUTER JOIN, besides other uses, is very useful in ETLs for doing
transformations on top of table differences. Using two outer joins, as
suggested in one of the above posts, unnecessarily overcomplicates
statements.
Stefan
On Monday, December 2, 2013 at 8:09:14 PM UTC-5, Michael Bayer wrote:
>
> if someone wants to pullreq the kw argument “full=True” on .outerjoin(),
> if it’s done effectively I won’t reject it.
>
>
> On Dec 2, 2013, at 5:43 PM, Jonathan Vanasco <[email protected]
> <javascript:>> wrote:
>
>
>
> On Monday, December 2, 2013 2:46:20 PM UTC-5, Michael Bayer wrote:
>>
>> well the alternative to full outer join is a union of two outer joins -
>> more tedious. “full outer join” isn’t in the library but you can just
>> subclass Join and do a @compiles to get that exact syntax.
>>
>
> you could also query the union of two outer joins, by treating it as a
> nested subquery. that is not only tedious, but painful and annoying. you
> could do it though!
>
> --
> 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 [email protected] <javascript:>.
> To post to this group, send email to [email protected]
> <javascript:>.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
