On Mon, Jun 21, 2021 at 12:04:48PM -0400, Mike Bayer wrote:
> hi -
>
Hello,
> can you please create a self-contained MCVE and post to
> https://github.com/sqlalchemy/sqlalchemy/issues - thanks.
I've created a ticket with a MCVE
https://github.com/sqlalchemy/sqlalchemy/issues/6661
Have a nice
hi -
can you please create a self-contained MCVE and post to
https://github.com/sqlalchemy/sqlalchemy/issues - thanks.
- mike
On Mon, Jun 21, 2021, at 5:25 AM, Julien Cigar wrote:
> ok .. :)
>
> Another regression from 1.3: I have two deferred column_property on my
> mapped class (1) and
ok .. :)
Another regression from 1.3: I have two deferred column_property on my
mapped class (1) and with (2) I'm getting a
sqlalchemy.exc.ProgrammingError: sqlalchemy.exc.ProgrammingError:
(psycopg2.errors.InvalidColumnReference) WITH query "parents" has 21
columns available but 23 columns
that's a really obscure API you found there. Coverage for that wasn't
carried along to 1.4 unfortunately so you'd need to assemble that list outside
of the and_() first for now.
On Fri, Jun 18, 2021, at 4:08 AM, Julien Cigar wrote:
> Hello,
>
> While updating SQLAlchemy dependency
On Fri, Jun 18, 2021 at 10:08:04AM +0200, Julien Cigar wrote:
> Hello,
>
> While updating SQLAlchemy dependency to 1.4 (from 1.3) I noticed that I
> couldn't use .append() on an existing sql.and_() clause .. is it
> expected..?
I forgot to add that the error I get is:
Traceback (most recent
Hello,
While updating SQLAlchemy dependency to 1.4 (from 1.3) I noticed that I
couldn't use .append() on an existing sql.and_() clause .. is it
expected..?
The problematic code is
https://gist.github.com/silenius/7d3043d64fddaa8474dcd062e23ced44 (line
18-21)
Another example that worked with
