On Tue, Oct 10, 2017 at 11:07 AM, Julien Meyer <[email protected]> wrote: > Hello, > > I have a problem when using an offset (with MSSQL) and joined relationships > : "Invalid column name '%(181351312 customerfollowupaction)s_tstamp'". > > The query works without offset. But when adding an offset, SQLAlchemy > creates an alias query with the row_number helper function. The "bug" is in > the outer select clause : all relationship fields are not "translated" by > SQLAlchemy (printed with %(...)s_column_name).
sounds like a bug. Can you please provide a complete test case that reproduces your issue? thanks! > > Any idea? > > Thanks > > > -- > 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. > --- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- 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. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
