From 8ddf2e94df70707b458528a437759b96046d3e01 Mon Sep 17 00:00:00 2001 From: Franck Cuny Date: Tue, 26 Nov 2013 10:36:10 -0800 Subject: Huge update. Moved all posts from textile to markdown. Updated all the CSS and styles. Added a new page for the resume. --- _posts/2008-06-21-debug-your-dbix-class-queries.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to '_posts/2008-06-21-debug-your-dbix-class-queries.md') diff --git a/_posts/2008-06-21-debug-your-dbix-class-queries.md b/_posts/2008-06-21-debug-your-dbix-class-queries.md index dc58280..7cb66c2 100644 --- a/_posts/2008-06-21-debug-your-dbix-class-queries.md +++ b/_posts/2008-06-21-debug-your-dbix-class-queries.md @@ -6,16 +6,16 @@ summary: In which I explain how to see SQL queries generated for DBIx::Class. If you use DBIx::Class and want to see what the SQL generated looks like, you can set the environment variable **DBIC_TRACE**. -```sh +{% highlight sh %} % DBIC_TRACE=1 my_programme.pl -``` +{% endhighlight %} And all the SQL will be printed on **STDERR**. If you give a filename to the variable, like this -```sh +{% highlight sh %} % DBIC_TRACE="1=/tmp/sql.debug" -``` +{% endhighlight %} all the statements will be printed in this file. -- cgit v1.2.3