I am not sure about python but ORM itself is problematic, Object Relational Mapping(ORM) when implemented is a solution for storing Objects(in memory) in relational data(rows/columns), you can think of this as like a projection operator in linear algebra, an n dimensional view of a m dimensional structure where n < m, often this works OK but there will always be cases where it causes more issues than its solves(often in the inverse map). With the advent of NoSql or the Json extensions in newer relational Postgres or Oracle db versions you can directly represent the Object in the db, no need for the relational mapping.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am not sure about python but ORM itself is problematic, Object Relational Mapping(ORM) when implemented is a solution for storing Objects(in memory) in relational data(rows/columns), you can think of this as like a projection operator in linear algebra, an n dimensional view of a m dimensional structure where n < m, often this works OK but there will always be cases where it causes more issues than its solves(often in the inverse map). With the advent of NoSql or the Json extensions in newer relational Postgres or Oracle db versions you can directly represent the Object in the db, no need for the relational mapping.