resurfacing this, as I'm facing something similar with pyramid.tm.
most of my problems on a new project stem from ZopeTransactionExtension
clearing everything out on a commit for a certain route (only one route
explicitly calls `transaction.commit`)
I'm fine with the additional selects being
Mike, you are a rock star! Thanks so much for all of the help. It worked
after we changed it like you said above. While we must keep the case
sensitivity to True for now, that's fine for us for now. Thank you so much
for your help!
On Tuesday, April 5, 2016 at 2:28:50 PM UTC-4, Mike Bayer
On 04/05/2016 02:15 PM, Douglas Eisenstein wrote:
Thanks Mike for the response and issue creation. So, I've set that case
sensitivity option to True, and we're getting another issue (edge case?)
whereby when we reflect a single table we are doing
Thanks Mike for the response and issue creation. So, I've set that case
sensitivity option to True, and we're getting another issue (edge case?)
whereby when we reflect a single table we are doing
Table(metadata=self._metadata, schema=namespace, name=name)
When this is ran I get:
>>>
On Monday, April 4, 2016 at 11:16:56 PM UTC-4, Mike Bayer wrote:
>
> i think the problem is that if you aren't nesting the JOIN and instead
> doing an implicit join, then things like joined eager loading don't work
> out as well. There's no subqueries in your primaryjoin I doubt there's
> a
