On Wed, 16 Jun 2021, Ryan Bandler wrote:
Yeah I connect to the DB over localhost:5432 via psql all the time and
also haven't had any issues connecting via psycopg2. I also have no issue
connecting to the database in sqlalchem, it's only an issue with
sqlacodegen.
Ryan,
Just to confirm,
Anyways guys I was able to fix the issue by installing a flask-specific
version of the same package (even though I am not using flask) and I was
able to get it to work just fine. Thanks everyone for your help.
On Wednesday, June 16, 2021 at 9:20:37 AM UTC-4 Ryan Bandler wrote:
> Yeah I connect
Yeah I connect to the DB over localhost:5432 via psql all the time and also
haven't had any issues connecting via psycopg2. I also have no issue
connecting to the database in sqlalchem, it's only an issue with
sqlacodegen.
On Tuesday, June 15, 2021 at 7:53:51 PM UTC-4 jonatha...@gmail.com
HI Simon -
I believe that example for now should vendor its own "copy()" function that
does what's needed. the function that's there is already un-doing some of the
work of the old copy() method in any case. I think for history table we need
column name, datatype, and maybe nullable
Hi all,
I'm updating an app from SA 1.3 to 1.4 and getting a SADeprecationWarning:
The Column.copy() method is deprecated and will be removed in a
future release. (deprecated since: 1.4)
The code triggering the warning is based on the versioned_history example:
On Mon, Jun 14, 2021 at 10:04:10AM -0400, Mike Bayer wrote:
> Buried deep in this example you are using the "relationship to aliased class"
> pattern, which is fine, not sure if that was in the previous example, but in
> this case this is the source of the issue.
>
> The approach to solving all
