Re: [sqlalchemy] Custom Compilation

2020-03-18 Thread Mike Bayer
On Wed, Mar 18, 2020, at 1:23 PM, Soumaya Mauthoor wrote: > Hello > > I have two uses cases: > > (1) drop cascade as option > I know I can use custom compilation to add cascade for postgres databases > using this example: >

[sqlalchemy] Custom Compilation

2020-03-18 Thread Soumaya Mauthoor
Hello I have two uses cases: (1) drop cascade as option I know I can use custom compilation to add cascade for postgres databases using this example: https://stackoverflow.com/questions/38678336/sqlalchemy-how-to-implement-drop-table-cascade Is it possible to use custom compilation to add

[sqlalchemy] Re: Problem with inserting row containing a value with type PATH of postgres with geoalchemy2

2020-03-18 Thread Jonathan Vanasco
I'm glad it's up and running for you! -- 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. ---

[sqlalchemy] Re: Warning about using backref with viewonly - how to make a two-way read-only relation?

2020-03-18 Thread Jonathan Vanasco
Tony, Mike helped me with a similar problem a few weeks ago: https://groups.google.com/d/msg/sqlalchemy/k4a-v2ebeJM/bj73xd4CFwAJ In his suggestion, I stash some mapper configuration data into `info`, then use the `mapper_configured` event to audit my configuration requirements. --

Re: [sqlalchemy] Warning about using backref with viewonly - how to make a two-way read-only relation?

2020-03-18 Thread Mike Bayer
On Wed, Mar 18, 2020, at 11:42 AM, Mike Bayer wrote: > > > On Wed, Mar 18, 2020, at 11:22 AM, Tony Hignett wrote: >> Hi, >> >> I'm trying to upgrade from 1.2.2 to 1.3.15 and a number of our relations >> have started generating these warnings: >> ``` >> SAWarning: Setting backref /

Re: [sqlalchemy] Warning about using backref with viewonly - how to make a two-way read-only relation?

2020-03-18 Thread Mike Bayer
On Wed, Mar 18, 2020, at 11:22 AM, Tony Hignett wrote: > Hi, > > I'm trying to upgrade from 1.2.2 to 1.3.15 and a number of our relations have > started generating these warnings: > ``` > SAWarning: Setting backref / back_populates on relationship to > refer to viewonly relationship will be

[sqlalchemy] Warning about using backref with viewonly - how to make a two-way read-only relation?

2020-03-18 Thread Tony Hignett
Hi, I'm trying to upgrade from 1.2.2 to 1.3.15 and a number of our relations have started generating these warnings: ``` SAWarning: Setting backref / back_populates on relationship to refer to viewonly relationship will be deprecated in SQLAlchemy 1.4, and will be disallowed in a future

[sqlalchemy] Re: Problem with inserting row containing a value with type PATH of postgres with geoalchemy2

2020-03-18 Thread Christos Ch
Yes you are right thank you! On Tuesday, March 17, 2020 at 7:41:58 PM UTC+2, Jonathan Vanasco wrote: > > > On Tuesday, March 17, 2020 at 12:06:36 PM UTC-4, Christos Ch wrote: >> >> I am running a service from a docker container >> > > The error is from psycopg2 and stating the function is not