oddly enough i just checked in a change to the logging methodology that would make this more difficult :) (since turning on "echo" means setting up a logging config now). the way "echo" was working, i.e. just saying "print", needed to be more configurable than that.
do you specfically need the exact SQL thats being sent over the wire, or can you just run str() on the statement objects ? it feels like this is a special need that would be addressed by a proxying ExecutionContext or similar. On Sep 25, 2006, at 12:11 PM, Rick Morrison wrote: > Anyone know if is there an easy way to echo individual statements > in SA? > > I know it's possible to do: > > x = engine.echo > engine.echo = True > > <SA statements> > > engine.echo = x > > But it would be nice to have a statement option for simple > interpreter-prompt debugging where you didn't have a ref to the > engine handy. > > > Rick > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > Sqlalchemy-users mailing list > Sqlalchemy-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
