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 3:45 AM Simon King wrote:
> On Fri, Jun 18, 2021 at 12:21 AM jca...@gmail.com
> wrote:
> >
> > Hi,
> > Does a means exist to generically call a local datetime func such that
> it renders as SYSDATE in Oracle and GETDATE() in SQL Server?
> >
> > Thanks,
> > jlc
> >
>
> Do
On Fri, Jun 18, 2021 at 12:21 AM jca...@gmail.com wrote:
>
> Hi,
> Does a means exist to generically call a local datetime func such that it
> renders as SYSDATE in Oracle and GETDATE() in SQL Server?
>
> Thanks,
> jlc
>
Do you need those functions explicitly? I think both databases support
the
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
