[Sqlalchemy-commits] commit/sqlalchemy: 6 new changesets

[Bitbucket <com...@bi...>]

6 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/51e1019f610f/
Changeset:   51e1019f610f
Branch:      None
User:        zzzeek
Date:        2013-06-04 22:21:25
Summary:     here's the flat join thing.  it just works.   Changing the existing compiled SQL assertions
might even be most of the tests we need (though dedicated sql tests would be needed anyway)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/58e917fe2de2/
Changeset:   58e917fe2de2
Branch:      None
User:        zzzeek
Date:        2013-06-04 22:48:14
Summary:     - eager loads
- two suite of SQL assertions converted

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/11578ba709ff/
Changeset:   11578ba709ff
Branch:      None
User:        zzzeek
Date:        2013-06-05 00:23:06
Summary:     - improve overlapping selectables, apply to both query and relationship
- clean up inspect() calls within query._join()
- make sure join.alias(flat) propagates
- fix almost all assertion tests

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c7b52003fb36/
Changeset:   c7b52003fb36
Branch:      None
User:        zzzeek
Date:        2013-06-05 00:43:59
Summary:     - add a flag to DefaultDialect for this so that people will have some
workaround

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ff2266bfac55/
Changeset:   ff2266bfac55
Branch:      None
User:        zzzeek
Date:        2013-06-05 00:49:24
Summary:     clean up the dialect selection thing here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/66b8ed40c350/
Changeset:   66b8ed40c350
Branch:      ticket_2587
User:        zzzeek
Date:        2013-06-05 00:58:24
Summary:     repair these tests now that we allow join from selectable to fromgrouping

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.