you can perhaps use a logging filter, just split the logs on a different token other than the newline, or write your own log routine using the before_cursor_execute event. there's a lot of ways to get this effect but none are more convenient than another.
On Apr 22, 2014, at 10:49 AM, lev katzav <kat...@gmail.com> wrote: > Hi all, > > I am execution a complicated query, > and when the query is written to the log, it breaks down into separate lines. > > This makes it really difficult to search the resulting log file for a query, > since grep will find only part of the query. > > Is there a way to force the query to be written in a single line? > > Thanks, > Lev. > > -- > 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 sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
