Kent jkentbo...@gmail.com wrote:
Mike,
When using use_ansi=False for Oracle (8) in conjunction with joinedload-ing
an inline view property, SQLAlchemy-0.8.7 renders an inner join instead of an
outer join. This has been fixed in SQLAlchemy-0.9.0, but, as I'm not
prepared for the
Mike,
When using use_ansi=False for Oracle (8) in conjunction with joinedload-ing
an inline view property, SQLAlchemy-0.8.7 renders an inner join instead of
an outer join. This has been fixed in SQLAlchemy-0.9.0, but, as I'm not
prepared for the migration yet, I was hoping and failing to find
So, in 0.7 expression.py has a non-public, underscored class
_FromGrouping instead of the public class FromGrouping
That should be just fine to use, correct?
On Wednesday, January 21, 2015 at 3:56:12 PM UTC-5, Michael Bayer wrote:
wow that is awful, how often do I fix a full blown bug, even
Here it is:
commit 85368d25ed158c85bd19f4a63400884ab1cda26a
Author: Mike Bayer m...
Date: Sat Jun 8 18:54:14 2013 -0400
get nested joins to render on oracle 8
Sounds like the right commit notes. You still maintaining 0.8? Should
that change be patchable in 0.7?
On Wednesday,
Hmmm 0.7 is missing expression.FromGrouping... I imagine that is a big
deal, isn't it, like not really patchable?
On Wednesday, January 21, 2015 at 3:11:29 PM UTC-5, Kent wrote:
Here it is:
commit 85368d25ed158c85bd19f4a63400884ab1cda26a
Author: Mike Bayer m...
Date: Sat Jun 8
try it!
Kent jkentbo...@gmail.com wrote:
So, in 0.7 expression.py has a non-public, underscored class _FromGrouping
instead of the public class FromGrouping
That should be just fine to use, correct?
On Wednesday, January 21, 2015 at 3:56:12 PM UTC-5, Michael Bayer wrote:
wow that
wow that is awful, how often do I fix a full blown bug, even write tests for
it, and don’t put anything in the changelog, no bug report or anything.
You can probably patch it to 0.8. Not sure about 0.7, but if 0.7 doesn’t have
FromGrouping there should still be some similar concept that can be
