[sqlalchemy] Common datetime call

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 -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE:

Re: [sqlalchemy] Ambiguous joins, relationships, and aliases

On Thu, Jun 17, 2021, at 1:04 PM, Dane K Barney wrote: > I have scoured the documentation looking for the preferred way of handling > ambiguous joins, and it seems to be through use of aliased tables, but I > still wonder if there's a better way. Intuitively, it seems like > relationships

[sqlalchemy] Ambiguous joins, relationships, and aliases

I have scoured the documentation looking for the preferred way of handling ambiguous joins, and it seems to be through use of aliased tables, but I still wonder if there's a better way. Intuitively, it seems like relationships hold enough information to make aliased tables unnecessary. But the

Re: [sqlalchemy] versioned_history example uses deprecated Column.copy() method

Thanks Mike, I'll see what I can do. Simon On Wed, Jun 16, 2021 at 1:26 PM Mike Bayer wrote: > > 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