Re: [sqlalchemy] row.Row and dict behavior in 2.0

2023-01-13 Thread mkmo...@gmail.com 
Hi Mike,

That's much more concise, thank you.

Previously I have always accessed the  `_asdict()` private member.

Thanks and best regards,

Matthew

On Thursday, January 12, 2023 at 11:00:58 AM UTC-8 Mike Bayer wrote:

>
>
> On Thu, Jan 12, 2023, at 1:46 PM, mkmo...@gmail.com wrote:
>
> Hi Mike,
>
> Thanks. I have a few cases where it is easiest if I have a plain dict 
> instead of a RowMapping. For example RowMapping is immutable, and isn't 
> playing nicely with my json encoder.
>
> What is your preferred method to convert to a plain dict?
>
>
> for row in result.mappings():
> d = dict(row)
>
> should do it
>
> the row was not mutable in 1.4, 1.3, etc. either, what did you do then ?
>
>
> Row._asdict()
> dict(RowMapping.items())
> something else? 
>
> Thanks and best regards,
>
> Matthew
>
>
> On Monday, January 9, 2023 at 6:00:08 PM UTC-8 Mike Bayer wrote:
>
>
>
> On Mon, Jan 9, 2023, at 8:50 PM, mkmo...@gmail.com wrote:
>
> Hello,
>
> It looks like in 2.0 we can no longer treat a row.Row as a dict. I have a 
> few cases where I want to do this, such as when I need to get a list of 
> columns, or when I don't know the column name in advance.
>
> rows = conn.execute(select(t.c.foo)).fetchall()
>
> rows[0].keys()  # Not Allowed
>
> rows[0][some_unknown_column]  # not allowed
>
> If we need to treat it as a dict, are we supposed to be calling:
>
> rows[0]._asdict()
>
> This works, but the only issue is that our IDEs flag this as accessing a 
> protected member of a class. Is there any alternative?
>
> Thanks and best regards,
>
>
> you have more options here than previously on how to treat rows, as tuples 
> or mappings, either up front or on a per-row basis.  the new API has been  
> available as of version 1.4.  Relevant links include:
>
> 1. announcement of change and rationale
>
>
> https://docs.sqlalchemy.org/en/14/changelog/migration_14.html#rowproxy-is-no-longer-a-proxy-is-now-called-row-and-behaves-like-an-enhanced-named-tuple
>
> 2. migration guide
>
>
> https://docs.sqlalchemy.org/en/14/changelog/migration_20.html#result-rows-act-like-named-tuples
>
> 3. new tutorial coverage
>
>
> https://docs.sqlalchemy.org/en/14/tutorial/dbapi_transactions.html#fetching-rows
>
> included is background on how to get mappings from a Row or how to get 
> RowMapping objects from a result up front using result.mappings().
>
>
>
>
>
>
>
> Matthew
>
>
> -- 
> SQLAlchemy - 
> The Python SQL Toolkit and Object Relational Mapper
>  
> http://www.sqlalchemy.org/
>  
> To post example code, please provide an MCVE: Minimal, Complete, and 
> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
> description.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sqlalchemy/10721070-ecf9-4438-87dc-a9ff6c13c0dan%40googlegroups.com
>  
> 
> .
>
>
>
> -- 
> SQLAlchemy - 
> The Python SQL Toolkit and Object Relational Mapper
>  
> http://www.sqlalchemy.org/
>  
> To post example code, please provide an MCVE: Minimal, Complete, and 
> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
> description.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sqlalchemy/624b2fdc-1c9d-4c3b-9424-f091b4be529an%40googlegroups.com
>  
> 
> .
>
>
>

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/3dc91ef7-585d-4085-8825-31bc39ccd2edn%40googlegroups.com.

Re: [sqlalchemy] row.Row and dict behavior in 2.0

2023-01-12 Thread Mike Bayer 


On Thu, Jan 12, 2023, at 1:46 PM, mkmo...@gmail.com wrote:
> Hi Mike,
> 
> Thanks. I have a few cases where it is easiest if I have a plain dict instead 
> of a RowMapping. For example RowMapping is immutable, and isn't playing 
> nicely with my json encoder.
> 
> What is your preferred method to convert to a plain dict?

for row in result.mappings():
d = dict(row)

should do it

the row was not mutable in 1.4, 1.3, etc. either, what did you do then ?

> 
> Row._asdict()
> dict(RowMapping.items())
> something else? 
> 
> Thanks and best regards,
> 
> Matthew
> 
> 
> On Monday, January 9, 2023 at 6:00:08 PM UTC-8 Mike Bayer wrote:
>> 
>> 
>> On Mon, Jan 9, 2023, at 8:50 PM, mkmo...@gmail.com wrote:
>>> Hello,
>>> 
>>> It looks like in 2.0 we can no longer treat a row.Row as a dict. I have a 
>>> few cases where I want to do this, such as when I need to get a list of 
>>> columns, or when I don't know the column name in advance.
>>> 
>>> rows = conn.execute(select(t.c.foo)).fetchall()
>>> 
>>> rows[0].keys()  # Not Allowed
>>> 
>>> rows[0][some_unknown_column]  # not allowed
>>> 
>>> If we need to treat it as a dict, are we supposed to be calling:
>>> 
>>> rows[0]._asdict()
>>> 
>>> This works, but the only issue is that our IDEs flag this as accessing a 
>>> protected member of a class. Is there any alternative?
>>> 
>>> Thanks and best regards,
>> 
>> you have more options here than previously on how to treat rows, as tuples 
>> or mappings, either up front or on a per-row basis.  the new API has been  
>> available as of version 1.4.  Relevant links include:
>> 
>> 1. announcement of change and rationale
>> 
>> https://docs.sqlalchemy.org/en/14/changelog/migration_14.html#rowproxy-is-no-longer-a-proxy-is-now-called-row-and-behaves-like-an-enhanced-named-tuple
>> 
>> 2. migration guide
>> 
>> https://docs.sqlalchemy.org/en/14/changelog/migration_20.html#result-rows-act-like-named-tuples
>> 
>> 3. new tutorial coverage
>> 
>> https://docs.sqlalchemy.org/en/14/tutorial/dbapi_transactions.html#fetching-rows
>> 
>> included is background on how to get mappings from a Row or how to get 
>> RowMapping objects from a result up front using result.mappings().
>> 
>> 
>> 
>> 
>> 
>> 
>>> 
>>> Matthew
>>> 
>>> 
>>> -- 
>>> SQLAlchemy - 
>>> The Python SQL Toolkit and Object Relational Mapper
>>>  
>>> http://www.sqlalchemy.org/
>>>  
>>> To post example code, please provide an MCVE: Minimal, Complete, and 
>>> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
>>> description.
>>> --- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "sqlalchemy" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to sqlalchemy+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sqlalchemy/10721070-ecf9-4438-87dc-a9ff6c13c0dan%40googlegroups.com
>>>  
>>> .
>> 
> 
> 
> -- 
> SQLAlchemy - 
> The Python SQL Toolkit and Object Relational Mapper
>  
> http://www.sqlalchemy.org/
>  
> To post example code, please provide an MCVE: Minimal, Complete, and 
> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
> description.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sqlalchemy/624b2fdc-1c9d-4c3b-9424-f091b4be529an%40googlegroups.com
>  
> .

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/4f191969-46b7-4f14-afd1-3cfb26002d24%40app.fastmail.com.

Re: [sqlalchemy] row.Row and dict behavior in 2.0

2023-01-12 Thread mkmo...@gmail.com 
Hi Mike,

Thanks. I have a few cases where it is easiest if I have a plain dict 
instead of a RowMapping. For example RowMapping is immutable, and isn't 
playing nicely with my json encoder.

What is your preferred method to convert to a plain dict?

Row._asdict()
dict(RowMapping.items())
something else? 

Thanks and best regards,

Matthew


On Monday, January 9, 2023 at 6:00:08 PM UTC-8 Mike Bayer wrote:

>
>
> On Mon, Jan 9, 2023, at 8:50 PM, mkmo...@gmail.com wrote:
>
> Hello,
>
> It looks like in 2.0 we can no longer treat a row.Row as a dict. I have a 
> few cases where I want to do this, such as when I need to get a list of 
> columns, or when I don't know the column name in advance.
>
> rows = conn.execute(select(t.c.foo)).fetchall()
>
> rows[0].keys()  # Not Allowed
>
> rows[0][some_unknown_column]  # not allowed
>
> If we need to treat it as a dict, are we supposed to be calling:
>
> rows[0]._asdict()
>
> This works, but the only issue is that our IDEs flag this as accessing a 
> protected member of a class. Is there any alternative?
>
> Thanks and best regards,
>
>
> you have more options here than previously on how to treat rows, as tuples 
> or mappings, either up front or on a per-row basis.  the new API has been  
> available as of version 1.4.  Relevant links include:
>
> 1. announcement of change and rationale
>
>
> https://docs.sqlalchemy.org/en/14/changelog/migration_14.html#rowproxy-is-no-longer-a-proxy-is-now-called-row-and-behaves-like-an-enhanced-named-tuple
>
> 2. migration guide
>
>
> https://docs.sqlalchemy.org/en/14/changelog/migration_20.html#result-rows-act-like-named-tuples
>
> 3. new tutorial coverage
>
>
> https://docs.sqlalchemy.org/en/14/tutorial/dbapi_transactions.html#fetching-rows
>
> included is background on how to get mappings from a Row or how to get 
> RowMapping objects from a result up front using result.mappings().
>
>
>
>
>
>
>
> Matthew
>
>
> -- 
> SQLAlchemy - 
> The Python SQL Toolkit and Object Relational Mapper
>  
> http://www.sqlalchemy.org/
>  
> To post example code, please provide an MCVE: Minimal, Complete, and 
> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
> description.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sqlalchemy/10721070-ecf9-4438-87dc-a9ff6c13c0dan%40googlegroups.com
>  
> 
> .
>
>
>

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/624b2fdc-1c9d-4c3b-9424-f091b4be529an%40googlegroups.com.

Re: [sqlalchemy] row.Row and dict behavior in 2.0

2023-01-09 Thread Mike Bayer 


On Mon, Jan 9, 2023, at 8:50 PM, mkmo...@gmail.com wrote:
> Hello,
> 
> It looks like in 2.0 we can no longer treat a row.Row as a dict. I have a few 
> cases where I want to do this, such as when I need to get a list of columns, 
> or when I don't know the column name in advance.
> 
> rows = conn.execute(select(t.c.foo)).fetchall()
> 
> rows[0].keys()  # Not Allowed
> 
> rows[0][some_unknown_column]  # not allowed
> 
> If we need to treat it as a dict, are we supposed to be calling:
> 
> rows[0]._asdict()
> 
> This works, but the only issue is that our IDEs flag this as accessing a 
> protected member of a class. Is there any alternative?
> 
> Thanks and best regards,

you have more options here than previously on how to treat rows, as tuples or 
mappings, either up front or on a per-row basis.  the new API has been  
available as of version 1.4.  Relevant links include:

1. announcement of change and rationale

https://docs.sqlalchemy.org/en/14/changelog/migration_14.html#rowproxy-is-no-longer-a-proxy-is-now-called-row-and-behaves-like-an-enhanced-named-tuple

2. migration guide

https://docs.sqlalchemy.org/en/14/changelog/migration_20.html#result-rows-act-like-named-tuples

3. new tutorial coverage

https://docs.sqlalchemy.org/en/14/tutorial/dbapi_transactions.html#fetching-rows

included is background on how to get mappings from a Row or how to get 
RowMapping objects from a result up front using result.mappings().






> 
> Matthew
> 
> 
> -- 
> SQLAlchemy - 
> The Python SQL Toolkit and Object Relational Mapper
>  
> http://www.sqlalchemy.org/
>  
> To post example code, please provide an MCVE: Minimal, Complete, and 
> Verifiable Example. See http://stackoverflow.com/help/mcve for a full 
> description.
> --- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sqlalchemy/10721070-ecf9-4438-87dc-a9ff6c13c0dan%40googlegroups.com
>  
> .

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/aeb7fb31-d5b1-4edd-b846-8cfbb435229a%40app.fastmail.com.

[sqlalchemy] row.Row and dict behavior in 2.0

2023-01-09 Thread mkmo...@gmail.com 
Hello,

It looks like in 2.0 we can no longer treat a row.Row as a dict. I have a 
few cases where I want to do this, such as when I need to get a list of 
columns, or when I don't know the column name in advance.

rows = conn.execute(select(t.c.foo)).fetchall()

rows[0].keys()  # Not Allowed

rows[0][some_unknown_column]  # not allowed

If we need to treat it as a dict, are we supposed to be calling:

rows[0]._asdict()

This works, but the only issue is that our IDEs flag this as accessing a 
protected member of a class. Is there any alternative?

Thanks and best regards,

Matthew

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sqlalchemy/10721070-ecf9-4438-87dc-a9ff6c13c0dan%40googlegroups.com.