Re: [sqlalchemy] dialect issue with pyodbc.Row type

Thanks for the insights On Tue, Jan 9, 2018 at 10:23 PM Mike Bayer wrote: > On Tue, Jan 9, 2018 at 8:45 PM, Russ Wilson wrote: > > So i loaded and tested the mmsql dialect and it gave the same results. It > > returns a list of pyodbc.Row > > > >

Re: [sqlalchemy] load_only change in 1.2.0?

On Wed, Jan 10, 2018 at 1:03 PM, Matt Schmidt wrote: > I have a small companion library that I wrote for model-to-dict > serialization. I just updated to 1.2.0 and one of my tests is failing -- > > https://gitlab.com/sloat/SerialAlchemy/blob/master/tests/test_to_dict.py#L193 > >

[sqlalchemy] Re: load_only change in 1.2.0?

On Wednesday, January 10, 2018 at 2:00:25 PM UTC-5, Matt Schmidt wrote: > > The version I upgraded from was 1.1.9, and I originally started the > project on 1.1.1. > > And you wrote that above and I totally missed that line - sorry. I'll pipe down for someone else to chime in now. --

[sqlalchemy] Re: load_only change in 1.2.0?

The version I upgraded from was 1.1.9, and I originally started the project on 1.1.1. I saw that bug and thought that was it, but then noticed that was a number of versions ago. On Wednesday, January 10, 2018 at 1:54:54 PM UTC-5, Jonathan Vanasco wrote: > > what version did you update from?

[sqlalchemy] Re: load_only change in 1.2.0?

what version did you update from? If this is the issue I am thinking about, that feature was added a long time ago... https://bitbucket.org/zzzeek/sqlalchemy/issues/3080 the issue in the ticket was the load_only added in the primary keys on joinedload but not subqueryload -- and the orm

[sqlalchemy] load_only change in 1.2.0?

I have a small companion library that I wrote for model-to-dict serialization. I just updated to 1.2.0 and one of my tests is failing -- https://gitlab.com/sloat/SerialAlchemy/blob/master/tests/test_to_dict.py#L193 In 1.1.x, it worked as expected, but in 1.2, the primary-key is added to the