[sqlalchemy] Re: Suggestion to support full outer joins

2007-02-20 Thread Michael Bayer

ive no problem with that feature, it was a TODO for sometime that got  
whacked from the sql.py module.  feel free to patch this up, though  
its a lot of work - to get it working on Oracle in ANSI mode using  
(+), maybe get DB's that dont support FULL OUTER JOIN to raise an  
error, etc.  "outerjoin()" functions need to default to LEFT OUTER  
JOIN but I dont think anyone is saying "join(... isouter=True)" these  
days.

On Feb 20, 2007, at 5:08 PM, Jonathan Ellis wrote:

>
> Instead of isouter argument to Join, have join_type.  Default to
> 'inner' but could also be 'left', 'right', or 'outer.'  (Or even
> 'natural' but that might be confusing b/c of Join's default behavior
> of joining by FK which is similar to but not the same as natural
> join.)
>
> (Of course, it's quite possible that SA already supports full outer
> joins and I just missed it, again. :)
>
> -Jonathan
>
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
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
-~--~~~~--~~--~--~---



[sqlalchemy] Re: Suggestion to support full outer joins

2007-02-20 Thread Jonathan Ellis

On 2/20/07, Jonathan Ellis <[EMAIL PROTECTED]> wrote:
> Instead of isouter argument to Join, have join_type.  Default to
> 'inner' but could also be 'left', 'right', or 'outer.'

should read "... or 'full,'" of course.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
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
-~--~~~~--~~--~--~---